Source-Changes-D archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: src

On Mon, Jul 05, 2010 at 04:43:14PM +0300, Antti Kantee wrote:
 > Seconded!  With even a modest amount of tests our file systems should
 > start behaving dramatically better.  Before it was easy'ish to partially
 > test one file system after a global change by recompiling kernel,
 > rebooting, and running an admittedly ad-hoc set of tests.  With Nicolas'
 > work it's trivial to test all of them within seconds of saving the source
 > file in the editor!

You can do a release build and anita run in seconds? Can I have a
build machine like that? :-)

 > > In this particular case, it'd have made sense (imo) to name the test
 > > program "t_rmdir" and the test case "race".  This way, t_rmdir can
 > > very easily accommodate future tests for rmdir(2) without the need to
 > > create a test program --
 > I'm still very unclear about the division between test program and
 > test case.  It seems rather arbitrary at times.  Maybe you can point us
 > to a set of suggested guidelines?

The way some of the tests are organized suggests that the intended
model is one test program per test victim (or per test victim and
substantially different testing harness) and then one test case per
bug affecting that victim.

Is that right?

David A. Holland

Home | Main Index | Thread Index | Old Index