David Brown wrote:
On Sat, Nov 01, 2008 at 08:44:08AM -0700, Darren New wrote:
I guess you could let the check-in provisionally pass if when you
check it in you say which tests you think you affected, and those
tests do what they're supposed to, then at lunch or in the evening you
run the whole suite of tests again.
It's smarter than this. It guess on tests based on other tests that
were changed at the same time as the files you modified in the change.
I guess that makes sense. You're saying if you check in
code_A, test_A1, test_A2 at the same time, then if you modify code_A,
it's more likely to run test_A1 and test_A2?
Nifty. I figured you'd have to do some sort of complicated analysis of
the tests themselves, but that certainly works.
Makes it hard to check in part of a change, I'd think, but maybe that's
helpful too.
--
Darren New / San Diego, CA, USA (PST)
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
