Ahh, I see what you mean. Without something like this, people might
write fixes for tests without knowing that they have fixes pending
already. Though it seems to me like the link here is in the wrong
direction - the test is slow changing, a long term asset, fixes come and
go. Therefore the test code shouldn't have to change when a test is
added/included/found faulty - it'll churn the tests (and their
maintainer) without need. 

Maybe what we need is a tool that leverages the BFAV (which already
knows what fixes are outstanding) to match failing tests to fixes that
claim to be relevant. So the convention would be about fixes somehow
addressing the test they're supposed to fix. Hmm, this sounds like it
could help with more automation later on...

Daniel

Marcus Denker <marcus at ira.uka.de> wrote:
> On Fri, Jun 20, 2003 at 12:28:29PM +0200, Daniel Vainsencher wrote:
> > How can you link between a test and it's status?
> > 
> I'd like to have somthing *very* simple at the beginning: If someone
> submits failing testcases and a FIX (which are most of the more
> complicated tests), then you should use the new feature in SUNIT 3.1
> to print out some comment with the failing test: 
>   [FIXED]
> or maybe even:
> 
>   [FIXED] http://linktoSQFIXES.html
> 
> very simple, but it will help to add those fixed more quickly.
> 
>    Marcus
> 
> -- 
> Marcus Denker marcus at ira.uka.de  -- Squeak! http://squeak.de