Last modified: 2011-09-12 14:18:21 UTC
Seems a bit pointless running the unit tests against phase3 when the only change has been say the RELEASE-NOTES or similar...
But it doesn't hurt. Creating a bunch of special cases does not seem worth to me the slight speed increase.
Retitling. I think being able to configure "run tests when /trunk/phase3 or /trunk/extensions changes" or any other set of paths would be nice. It's true, running parser tests when somebody updated their USERINFO or something in /trunk/tools However, I agree with Bryan that we shouldn't make a billion special cases, so I think this should be very general. Don't need to say "unless only X Y or Z changed, then skip it" In any case, I removed our crappy test system in r69385 (which had been broken forever). Marking this LATER, for revival one day once someone puts a new test system into Code Review.
(In reply to comment #2) > Retitling. I think being able to configure "run tests when /trunk/phase3 or > /trunk/extensions changes" or any other set of paths would be nice. It's true, > running parser tests when somebody updated their USERINFO or something in > /trunk/tools > ...would be pointless.
We're not integrating test running with CR again -> WONTFIX.
