Changes between Version 119 and Version 120 of TestCaseManagementPlugin

Timestamp:

May 6, 2022, 5:45:51 AM (19 months ago)

Author:

figaro

Comment:

Cosmetic changes

TestCaseManagementPlugin

@@ -40 +40 @@
 === Example
 
-Take the testcases that you've written in a Word doc or Excel spreadsheet and put one test case into one xml document. Check the testcases into Subversion (see below). There has been some feedback that this may end up in a large set of test cases, which is only true if you write test cases in scripted form: "Testcase 1: click the submit button... end of test case".
+Take the testcases that you've written in a Word doc or Excel spreadsheet and put one test case into one XML document. Check the testcases into Subversion (see below). There has been some feedback that this may end up in a large set of test cases, which is only true if you write test cases in scripted form: "Testcase 1: click the submit button... end of test case".
 
 === Brief Digression
 
-My personal philosophy is to encourage people to write work flow or task based driven testcases and have the tester use their brains to find issues. I call it '''script based exploratory testing'''. Check out Exploratory testing by James Bach at http://satisfice.com. If they need to look at the UI in very high detail then the test case could simply be "compare the UI to the mockup and here's the link to the screen shot".
+My personal philosophy is to encourage people to write work flow or task based driven testcases and have the tester find issues. I call it '''script based exploratory testing'''. Check out Exploratory testing at [http://satisfice.com James Bach's website]. If they need to look at the UI in high detail, then the test case could simply be "compare the UI to the mockup and here's the link to the screen shot".
 
 === Grouping testcases together
 
-You can specify collection of test cases (for example a smoke test) by specifying which test cases belong to a test template. This information is also specified in an xml file.
+You can specify collection of test cases (for example a smoke test) by specifying which test cases belong to a test template. This information is also specified in an XML file.
 
 Note this plugin is designed to work with Subversion, although no specific Subversion code is used. Potentially this plugin works with other Trac supported configuration management systems.
@@ -119 +119 @@
  1. Click on the TestManagement tab on the main Trac menu.
  1. Click on the Test Run link.
- 1. Select users to assign testcases to (these have to be known users to the Trac system).
+ 1. Select users to assign testcases to, and these have to be known users to the Trac system.
  1. Select the appropriate version, and/or milestone/sprint for this testrun.  
  1. Select the testcases, and/or the appropriate test template.
@@ -193 +193 @@
 }}}
 
-I've added some helpful debugging/error checking that should help if an error occurs. The most likely error is specifying the relative path to the testcases incorrectly.
+Some helpful debugging/error checking has been added that should help if an error occurs. The most likely error is an incorrect specification of the relative path to the testcases.
 
 == Recent Changes