[bind10-dev] testing, was Dummy DHCPv6 component review request
Shane Kerr
shane at isc.org
Wed Jun 22 10:41:07 UTC 2011
Tomasz,
On Mon, 2011-06-20 at 20:24 +0200, Tomasz Mrugalski wrote:
> Are there any documents regarding test designs or test strategy? I
> haven't read anything bind10 specific, just looked at existing code and
> wrote something similar
Hm... perhaps there are not.
I think we have the following general guidelines:
* Every line of code should be tested
* Every function should be called with normal and abnormal
conditions
* Every defect should be reproduced in a test before the fix is
made
* Tests should not require manual setup
* Tests should run quickly (no sleep() calls, please)
I'll let others comment on this thread, and then put this in the Wiki if
we have consensus.
> I noticed that make check aborts on first failed test. Is there a way to
> run the tests to continue and then present a summary (e.g. 5 out of 235
> tests failed)?
This is actually an anti-goal of testing, AIUI. All tests should work
all of the time, so a broken test should cause immediate pain which will
then be fixed.
There may be a way to do this, but I don't know what it is. :)
--
Shane
More information about the bind10-dev
mailing list