Does anyone know how to delete test run information. For example, I have a group of testers who are new to TestDirector. They have entered their manual test cases into TD. Some have practiced executing them from TD. Now TD has a history for the test, when in reality we haven't run any real tests. This is effecting the way our requirements tree appears because next to each requirement the status reads as Passed, Failed, Not Completed, etc. We want all of the requirements status fields to read as No Run. Does anyone know how to delete or reset the history? I can't find any info in either the user's guide or the admin guide.
I'm using version 6.02 so the following may not apply. Steps are:
<LI>With the "Run Tests" tab active,
<LI>click on the Test Set you want to remove run information from,
<LI>Click the Run menu item,
<LI>Select "Reset Test set"
<LI>answer Yes | No as your conscience dictates.
If there's not an equivalent function in the version you are using, perhaps in the next release (7.5?) there will be?
------------------ If we cease to become better, we will one day cease to be good. -Thomas Acquinas
QUALITY . . . is like buying oats. If you want nice, clean, fresh oats, you must pay a fair price.
However, if you can be satisfied with oats that have already been through the horse . . . that comes a little cheaper.
To walterj: Your suggestion works but isn't enough. You need to clean up more fields, but the result isn't consistent because it doesn't roll-up to Requirements level. A more comprehensive, yet not full, list is:
UPDATE testcycl SET TC_STATUS = 'No Run'
UPDATE testcycl SET TC_VTS = NULL
UPDATE testcycl SET TC_TESTCYCLE_VER_STAMP = 0
UPDATE testcycl SET TC_EXEC_DATE = NULL
UPDATE testcycl SET TC_EXEC_TIME = NULL
UPDATE testcycl SET TC_TESTER_NAME = NULL
UPDATE testcycl SET TC_USER_01 = NULL
UPDATE test SET TS_TEST_VER_STAMP = 1
UPDATE test SET TS_EXEC_STATUS = 'No Run'
UPDATE test SET TS_VTS = 0
To rwgreen1173: This is good, it does roll-up to Requirements level. The snag is that you have to do this for every test.
I have escalated this problem to MI support, they don't have a solution yet. They, in turn, escalated it to Development.
[This message has been edited by Asi (edited 09-02-2002).]