[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: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-01 22:55:08 CEST

Kieran <kieran@esperi.demon.co.uk> writes:
> 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?

There are tests attached to some issues.

> 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.

We break regression tests *all the time*, in the course of developing
new code. Of course, you don't see that code get checked in, because
the regression tests told us not to :-).

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

So the proposal is basically to include currently failing tests in the
dist? That one can do right now. Just put the test in a foo_test.py
file, but don't add it to the test_list[], so it doesn't get run.
People have done that before plenty of times, nothing wrong with it.

If you want a way for people to run all currently failing tests, I'm
not sure what the point is... If someone's working on a specific bug,
they can run that test manually very easily. If they want to find out
what bugs need to be fixed, they can look in the issue tracker.

I'm not saying it's a bad idea, I just am not seeing the purpose.
Please enlighten?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 23:10:06 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.