Changes between Version 102 and Version 103 of TestCaseManagementPlugin

Timestamp:

Oct 1, 2008, 7:31:09 PM (16 years ago)

Author:

anonymous

Comment:

--

TestCaseManagementPlugin

@@ -21 +21 @@
 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.  As they complete a testing task they set the TRAC ticket to closed.    
 
-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.
+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).  The testcase is in subversion, while a test instance (in the form of a TRAC ticket), is in TRAC.  
@@ -32 +32 @@
 
 === Example... ===
-Take the testcases that you've written a in a word doc or excel and put one test case into one xml document.  Check the testcases into subversion (more on that below).  I've heard some feedback that potentially this ends up in a huge set of test cases.  That's only if you write test cases in the form : "Testcase 1: click the submit button...end of test case".
+Take the testcases that you've written in a word doc or excel and put one test case into one xml document.  Check the testcases into subversion (more on that below).  I've heard some feedback that potentially this ends up in a huge set of test cases.  That's only if you write test cases in the form : "Testcase 1: click the submit button...end of test case".
 
 === Brief Digression ===