Last modified 17 years ago
Last modified on 09/23/08 14:32:21
Analysis
Overview
Maintenance depends on test tracking setup. The maintenance should be performed monthly.
Task requirements
- Review existing tests.
- Review test current progress. Discuss with team problem tests.
- Review tickets of passed tests. If the test was failing but now is passing, close the ticket.
- Review if there are new basic tests.
- Mark needed tickets as unplanned and schedule them for a corresponding milestone.
Task result
The result should be stored in a log file in the wiki for example. Decide if this is the best way to keep information about maintained tracker.
Implementation idea
Create SCS_TEST_TRACKING_MAINTAINCE? and split it into 12 sections. Name each section with milestone and date. Fill in first section (for this milestone). Define rules about this document.
Related
How to demo
You should be able to present task progress by showing SCS_TEST_TRACKING_MAINTAINCE?
Design
Implementation
Testing
Log