From: Sean O'Dell <sean@...>
Date: 2004-07-07T05:28:46+09:00
Subject: Re: Bugtracking & UnitTests == good?

On Tuesday 06 July 2004 12:31, Lennon Day-Reynolds wrote:
>
> How about this: each new bug reporter has a status method
> automatically associated with it, which is a test case for that issue.
> The default status code always returns an error, so before an issue
> can be closed, someone must either manually write a test case which
> can then be checked to determine the issue status, or they must
> explicitly reassign a different "stock" status method which does not
> raise an exception (and possibly returns some symbolic value like
> "WorkingAsDesigned", or "NotReproduceable", which can go into a full
> test report).

This is an excellent idea, even if combined with a system that allows users to 
submit their own unit tests.  The user-submitted unit test could be disable 
until a developer has looked at it for security and then it could be added to 
the battery of tests.

> Unforunately, it seems like it would require a huge amount of trust in
> your users, or tightly-restricted permissions for who could write such
> cases, since you would be (presumably) accepting live code through the
> web, with all of the security implications that causes.

I think perhaps the cadre of developers for a given project could all be given 
the ability to review and "enable" user-submitted unit tests.

	Sean O'Dell