Changes between Version 3 and Version 4 of SCS_TEST_TRACKING_MAINTAINCE_R0


Ignore:
Timestamp:
09/18/08 17:37:58 (17 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SCS_TEST_TRACKING_MAINTAINCE_R0

    v3 v4  
     1= Analysis = 
     2== Overview == 
     3Maintenance depends on test tracking setup. The maintenance should be performed monthly.  
     4== Task requirements == 
    15 * Review existing tests. 
    26 * Review test current progress. Discuss with team problem tests. 
    37 * Review tickets of passed tests. If the test was failing but now is passing, close the ticket. 
    48 * Review if there are new basic tests. 
     9 * Mark needed tickets as unplanned and schedule them for a corresponding milestone. 
     10== Requirements to the task result == 
     11The 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. 
     12== Implementation idea == 
     13Create [wiki: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. 
     14== Related == 
     15[wiki:SCS_TEST_TRACKING_SETUP_R0] 
     16= Design = 
     17= Implementation = 
     18= Testing =