On Sat, Nov 01, 2008 at 08:09:33AM -0700, Darren New wrote:
David Brown wrote:
It's not a previous test that fails, but one that you have to write as
part of the existing checkin. In other words, all commits must
include a test that passes, and if the test is run against the current
basline, it must fail.
I see. Every checkin has to have *more* tests that pass that didn't pass
last time. Very cool idea, especially on a project you know is going to
get big when you start (and which you have some idea of what you want it to
do when you're done). :-)
Although it's also permitted to just change a testcase, say to find an
additional corner case or something like that.
The main bottleneck we started running into is that the whole test
suite was taking longer and longer to run, which kind of worked
against the small changeset model it otherwise encouraged. Aegis does
had support for trying to determine a subset of useful tests to run,
but it isn't quite as solid as running the whole testsuite.
David
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
