Changes between Version 67 and Version 68 of TestCaseManagementPlugin


Ignore:
Timestamp:
May 21, 2008 9:49:42 PM (6 years ago)
Author:
edunne
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestCaseManagementPlugin

    v67 v68  
    3232Some of the common problems that any testcase management tool faces are: 
    3333 
    34 1. versioning of the testcases (taken care of by subversion) 
     341. versioning of the test cases (taken care of by subversion) 
    3535 
    36362. '''reporting (taken care of by trac custom ticket reports)''' 
     
    4040So what is a test run? 
    4141 
    42 A test run is specific set of test cases for a particular milestone or version of the software under test for a particular tester.  Each tester owns a single instance of a test case in the form of a ticket.  This allows you to track the progress of individual testers as they complete their set of testcases.  This is really powerful because you can take full advantage of the custom reporting engine in TRAC to look for open tickets of type testcase that belong  to a particular tester, and also monitor the progress of a group of testers.  There was some confusion about this as it seemed like a single ticket would be "owned" by multiple testers.  TRAC's data model makes this impossible (also I think that assigning test tickets in that way would be really clunky).  Essentially what happens is the testcase is an xml document stored in subversion.  The testcasemanagementplugin creates a ticket with the test case details as the ticket description and assigns that ticket to a specific tester: one ticket per tester per testcase. 
     42A test run is specific set of test cases for a particular milestone or version of the software under test for a particular tester.  Each tester owns a single instance of a test case in the form of a ticket.  This allows you to track the progress of individual testers as they complete their set of test cases.  This is really powerful because you can take full advantage of the custom reporting engine in TRAC to look for open tickets of type testcase that belong  to a particular tester, and also monitor the progress of a group of testers.  There was some confusion about this as it seemed like a single ticket would be "owned" by multiple testers.  TRAC's data model makes this impossible (also I think that assigning test tickets in that way would be really clunky).  Essentially what happens is the testcase is an xml document stored in subversion.  The testcasemanagementplugin creates a ticket with the test case details as the ticket description and assigns that ticket to a specific tester: one ticket per tester per testcase. 
    4343 
    4444The advantage of having a testcase management tool in trac is that it removes the need to have yet another system that manages testcases...with all the usual problems of maintaining user accounts, system upgrades, and licensing issues.  The other advantage is that it adds more transparency to the testing process as the tool and any testcases are right there for anyone to see.