Changes between Version 4 and Version 5 of SCS_TEST_TRACKING_MAINTENANCE_R2


Ignore:
Timestamp:
12/15/08 11:32:24 (16 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SCS_TEST_TRACKING_MAINTENANCE_R2

    v4 v5  
    22 
    33[[TicketQuery(summary=SCS_TEST_TRACKING_MAINTENANCE_R2, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] 
    4  
    5  
    6  
    74 
    85= Analysis = 
    … …  
    107 
    118== Overview == 
    12 ^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^ 
     9Create test plans for Iteration 1 and Iteration 2. 
    1310 
    1411== Task requirements == 
    1512 * Ensure execution of test plans in !TestLink is possible by "tester" users. 
     13 * Create a test plan for Iteration 1 
     14 * Create a test plan for Iteration 2 
     15 * Choose and create a list of tasks that should have test cases for Iteration 3 
    1616 
    1717== Task result == 
    … …  
    1919 
    2020== Implementation idea == 
     21Assigned to should be set to all in view. 
    2122{{{ 
    2223Filter Test cases a user with tester role can VIEW depending on test execution assignment.