id	summary	reporter	owner	description	type	status	priority	component	severity	resolution	keywords	cc	release
7487	Add multiple test plans capability	seccanj	seccanj	In the long run, it would be useful (but not trivial to\r\n  implement) to differentiate between the definition of the\r\n  tests and running a test campaign. An example: I have a\r\n  software product, a plugin for Trac. Before doing a release\r\n  "1.0" I have to perform some interactive tests. Therefore\r\n  I start a new test campaign with svn revision 1234, where\r\n  all test verdicts "Untested". Let's say, one or two tests\r\n  failed. I conclude the test campaign unsuccessful. Now I\r\n  have to fix the bugs and have to start a new test campaign,\r\n  again with all test verdicts set to "Untested".	enhancement	closed	normal	TestManagerForTracPlugin	normal	fixed		rjollos	0.11