Changes between Version 52 and Version 53 of TestCaseManagementPlugin


Ignore:
Timestamp:
Apr 16, 2008, 5:49:35 PM (16 years ago)
Author:
ken.stricklett@…
Comment:

Grammatical corrections, also changed references to 'trac.config' to 'trac.ini'.

Legend:

Unmodified
Added
Removed
Modified

  • TestCaseManagementPlugin

    v52 v53  
    3636== Configuration steps required ==
    3737
    38 1. create a testcases directory within an existing subversion project.  This is where your testcases and your testtemplates.xml file goes.  We typically structure our development projects with a main project directory and then a source and build subdirectory.  So when you add the testcases directory you might have something like this:
     381. Create a testcase directory within an existing subversion project.  This is where your testcase and testtemplate files go.  We typically structure our development projects with a main project directory and then a source and build subdirectory.  So when you add the testcase directory you might have something like this:
    3939
    4040project/source/ <-- checked into subversion [[BR]]
    … …  
    4343
    4444
    45 The nice thing about this is you add a lot more transparency to the testing process as testcases are bundled and versioned with the source code
    46 
    47 2.  Add testcases and commit those testcases to your subversion repository using the example format (see attachment for correct XML format of the testcase file).
    48 
    49 3.  Create a testtemplate file called testtemplates.xml, then specify which tests belong to which test tempaltes, for example the smoke-test (see attachment for correct XML format of the test templates file).  Not all tests have to belong to a template, it's just a convient way to group tests together.  This file goes into the same project/testcases directory.
    50 
    51 4.  add to the trac.config file a new section:
     45The nice thing about this is you add a lot more transparency to the testing process as testcases are bundled and versioned with the source code.
     46
     472.  Add testcases and commit those testcases to your subversion repository using the example format (see attachment for correct XML format of testcase files).
     48
     493.  Create a testtemplate file called testtemplates.xml, then specify which tests belong to which test templates, for example the smoke-test (see attachment for correct XML format of the test templates file).  Not all tests have to belong to a template, it's just a convient way to group tests together.  This file goes into the same project/testcases directory.
     50
     514.  Add the following new section to the trac.ini file:
    5252
    5353{{{
    … …  
    62625. '''[http://trac.edgewall.org/wiki/TracAdmin add a new ticket type] called testcase''' 
    6363
    64 6. I also add a custom ticket type in the trac.config file for reporting purposes (although this is not required yet...just really useful)
     646. I also add a custom ticket type in the trac.ini file for reporting purposes (although this is not required yet...just really useful)
    6565
    6666{{{
    … …  
    7272}}}
    7373
    74 7. enable the plugin either through the trac admin plugin or by modifying the trac.config file:
     747. Enable the plugin either through the trac admin plugin or by modifying the trac.ini file:
    7575{{{
    7676[components]
    … …  
    7878}}}
    7979
    80 8. restrict ticket owners to only known users of the system.  You do this by looking for the line retrict_owner in the conf file.
     808. Restrict ticket owners to only known users of the system.  You do this by looking for the line retrict_owner in the trac.ini file.
    8181This is actually necessary because of an oversight on my part.  I incorrectly assumed that most people would have turned this on.
    8282{{{