You're welcome to run all the unit tests for projects A, B and C when you've made a change to project B. I was just presuming that if unit tests are being observed that projects A and C would be passing their tests already, since no changes were made yet locally.
Of course, stating that explicitly, it doesn't sound like a valid assumption. So running all tests regularly may be good practice so that everyone knows what tests aren't passing. The more people paying attention, the more likely that they're addressed, I would hope. Though an alternative effect is that people become desensitized to failing tests. On Jan 24, 1:56 pm, "laurel" <[EMAIL PROTECTED]> wrote: > Why don't we run all of the unit tests, instead of just the ones within > the project we've changed? Is it simply a scaling issue that needs to > be addressed? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
