Changes between Version 1 and Version 2 of SCS_TEST_TRACKING_MAINTENANCE_R0


Ignore:
Timestamp:
09/29/08 14:31:13 (17 years ago)
Author:
todor
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SCS_TEST_TRACKING_MAINTENANCE_R0

    v1 v2  
    11[[BackLinksMenu]] 
    22= Analysis = 
    3  This task includes maintaining the issue tracker.  
    4  
    53== Overview == 
    6  * Maintain the issue tracker regularly; 
    7   * Delete, fix, group, etc - tickets. 
    8   * Make sure tickets are up to date and generally correct. 
    9  * Define and create useful Reports; 
    10  * Review existing tickets.  
    11  * Look for duplicate issues and remove them. 
    12  * Look for unassigned tickets and assign them. 
    13  * Send reminders to owners of tickets without progress (look for comments that contain "estimate" "this will be fixes after" "this can't be fixed" etc.) 
    14  * Notify the team if the count of non-closed tickets is huge (in process of work we should consider what "huge count of tickets" mean. 
    15  * Notify the team for other issues you consider abnormal. 
    16  
     4Maintenance depends on test tracking setup. The maintenance should be performed monthly.  
    175== Task requirements == 
    18  * Issue Tracker should be well organized. 
    19  * Issue tracker should be up-to-date. 
    20  * Issue tracker should be fully consistent. 
    21  
    22 == Task Result == 
    23  * An easily maintainable tracker. 
    24  
     6 * Review existing tests. 
     7 * Review test current progress. Discuss with team problem tests. 
     8 * Review tickets of passed tests. If the test was failing but now is passing, close the ticket. 
     9 * Review if there are new basic tests. 
     10 * Mark needed tickets as unplanned and schedule them for a corresponding milestone. 
     11== Task result == 
     12The 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. 
    2513== Implementation idea == 
    26  * Review all reports. 
    27  * Review all tickets. 
    28  * Review owners of tasks. 
    29  * Review components. 
    30  * Create Severities. 
    31  
     14Create [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. 
     15== Related == 
     16[wiki:SCS_TEST_TRACKING_SETUP_R0] 
    3217== How to demo == 
    33  * Open http://asteasolutions.net:7080/sophie2 
    34  * Click on 'View Tickets' in the main tab-bar. 
    35  * Use reports to browse reports. 
    36  * Explain the different reports. 
    37  
     18You should be able to present task progress by showing [wiki:SCS_TEST_TRACKING_MAINTAINCE] 
    3819= Design = 
    39 Check the Overview requirements. 
    40  * Review all reports. 
    41  * Review all tickets. 
    42  * Review owners of tasks. 
    43  * Review components. 
    44  * Create Severities. 
    4520 
    4621= Implementation = 
     22 
    4723= Testing = 
     24 
    4825= Log = 
    49 [[Include(wiki:SCS_ISSUE_TRACKER_MAINTAINCE_R0_LOG)]] 
     26[[Include(wiki:SCS_TEST_TRACKING_MAINTAINCE_R0_LOG)]]