[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Test Strategy

From: Kieran <kieran_at_esperi.demon.co.uk>
Date: 2002-08-01 22:43:16 CEST

On 1 Aug 2002, Karl Fogel wrote:

> Kieran <kieran@esperi.demon.co.uk> writes:
> > Might it be an idea to split tests into "regression" and "bugs"?
> > That might encourage people to write or solitcit tests before
> > bug-hunting, which I think would be a win in the long-run.
> What prevents people from writing tests for their bug reports or
> patches is lack of time, not a matter of labeling. There's no real
> difference between a "bug test" and a "regression test". Before a fix
> is committed, the test is a reproduction recipe; after the fix is
> applied, the same test is now a regression test.
I don't believe this is the whole story. You're trying to say that
no developer had the time to write even one bug test?

At the moment, I don't think we have any "bug tests". I'm new,
but I haven't seen any tests fail yet that I didn't write myself.

And I'm not all that surprised, since if I'd seen a failed test in my
build, I'd be a bit worried. Since there are of the order of 50 open
bugs, 50 failed tests would cause a flood of mail to the list.

Since I'm just shooting at the status quo, here's something concrete
for discussion, which should avoid the flood of mail:

Idea 1:
In tests/clients/cmdline, change the names to add the word
regression, as in stat_tests.py -> stat_tests_regression.py, then
add stat_tests_bugs.py. Each test in ..._bugs would ideally include
reference to an issue number.

Idea 2:
Create 2 directories tests/client/cmdline/stat_tests_regression and
.../stat_tests_bugs. In here, add single-test files. This would
make moving tests from bugs to regression easier.

"make check" would run the regression tests, and "make check-all"
would run all the tests

Of course, this doesn't deal with the lack of time at all. Anyway,
should I shut up, or does my idea have merit?



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 22:47:47 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.