Date: Fri, 18 Oct 2002 11:42:23 +0200 From: "Fischer, Oliver" <plexus@snafu.de> To: Chris BeHanna <behanna@zbzoom.net> Cc: FreeBSD-Stable <stable@freebsd.org> Subject: Re: freebsd test matrix Message-ID: <3DAFD77F.7080902@snafu.de> References: <20021018034039.F1275-100000@topperwein.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris BeHanna wrote: > Ideally, each developer will have a set of unit tests for what > (s)he is working on, that could, with some massaging, be plugged into > a larger harness to do nightly regression testing (perhaps via > tinderbox). The trouble is keeping the tests up-to-date. Invariably, So the question is, who is writting the tests. In the company I am working in, each developer writes its own unittests ans has to run the whole testsuite every day. In the company of a friend of mine, the developers writes their own tests and the external QA writes tests too. The QA tests the public behavior the developers concentrate on the internals of the system. Here we have one unbreakable rule. No release if a single test fails. > what the tests are testing ends up changing underneath them, leading > to spurious failures in the test report. Ok this is true. But at least you will see that something is 'broken' from the view of the tests. I thing it is very important to have a system to collect the reports and see which test fails where. Then you can decide if the test is right, it is outdated or simply a dependency.... Bye Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DAFD77F.7080902>