Changes between Version 2 and Version 3 of SCS_TEST_TRACKING_SETUP_R0


Ignore:
Timestamp:
09/04/08 12:41:48 (17 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SCS_TEST_TRACKING_SETUP_R0

    v2 v3  
    1 Setup the test tracker. If we choose trac some tweaks are needed. In New Ticket: 
    2  * Type - discuss what other types should be used. 
    3  * Components - Application, Sever, Community Server. Discuss if more are needed. 
    4  * Milestones - Add appropriate milestones (12) You may consider useful renaming milestones in on of the following ways:  
    5   * m1, m2, m3, m4, m5, a1, a2, a3, b1, b2, b3, final. 
    6   * milestone1, milestone2, milestone3, milestone4, milestone5, milestone6, alpha1, alpha2, alpha3, beta1, beta2, beta3, final. 
    7   * m1, m2, m3, m4, m5, m6(a1), m7(a2), m8(a3), m9(b1), m10(b2), m11(b3), m12(final). 
    8  
    9  * Versions - Pre 1.0; 1.0; post 1.0. 
    10  * Document the setup for later use (re-setup). 
     1Choose a test tracking system (ex: TCW). Test tracking system should support: 
     2 * user accounts 
     3 * good relation (integration) with issue tracker 
     4 * general tests - this section should contain test that should be repeated every month for example.