From: Charles Mills <cmills@...>
Date: 2004-07-07T04:39:32+09:00
Subject: Re: Bugtracking & UnitTests == good?

On Jul 6, 2004, at 11:17 AM, martinankerl at eml dot cc wrote:

> Hi all! I am afraid this post is a bit offtopic. If you are not 
> interested in Bugtracking and Unit Tests, read no further! :-)
>
> At the moment I am playing with the idea of writing a simple 
> bugtracking system in Ruby. I thought that it would be a cool idea to 
> integrate Unit Tests with such a system: Every reported bug should get 
> a unit test assigned. If a unit test fails, the bug is automatically 
> reopened. When the tests is successful, it is closed. I have not 
> really thought this through, I am just asking if people here think 
> this is be a good idea or not.
>
> martinus
>

Seems like a great way to prevent bugs from coming back to life.  The 
Pragmatic Programmer talks about the importance of adding tests for 
each bug that is discovered.  If you had a test script for every bug 
that popped up you would end up with lots of files.  Although I guess a 
test script could just be a string/record in a database which is used 
to generate a temp file when the tests actually needs to be run (or 
just pipes a script into ruby).  Using a database would also help solve 
the problem of creating a link between the bug report and the unit 
test....
Sounds like a major project.  I would be interested in the results.
-Charlie