In the long run, it would be useful (but not trivial to
implement) to differentiate between the definition of the
tests and running a test campaign. An example: I have a
software product, a plugin for Trac. Before doing a release
"1.0" I have to perform some interactive tests. Therefore
I start a new test campaign with svn revision 1234, where
all test verdicts "Untested". Let's say, one or two tests
failed. I conclude the test campaign unsuccessful. Now I
have to fix the bugs and have to start a new test campaign,
again with all test verdicts set to "Untested".
