Changes between Version 34 and Version 35 of TestManagerForTracPlugin

Timestamp:

Oct 9, 2010, 3:05:59 PM (14 years ago)

Author:

Roberto Longobardi

Comment:

--

TestManagerForTracPlugin

@@ -14 +14 @@
 Multiple Test Plans can be associated to any Test Catalog, in order to keep track of the execution of the corresponding Test Cases in a particular testing context.
 
-A generic, customizable '''Workflow Engine''' is provided as a separate plugin in the package, which allows you to associate custom workflows to any Resource in Trac, including Wiki pages and any custom object handled through a Resource Manager. This can be done very easily by adding as little as [wiki:TestManagerForTracPluginWorkflow a few lines of code] to the component which manages the User interface.
+A generic, customizable '''[wiki:TestManagerForTracPluginWorkflow Workflow Engine]''' is provided as a separate plugin in the package, which allows you to associate custom workflows to any Resource in Trac, including Wiki pages and any custom object handled through a Resource Manager. This can be done very easily by adding as little as [wiki:TestManagerForTracPluginWorkflow a few lines of code] to the component which manages the User interface.
 
 All of the test objects, i.e. catalogs, test cases, test plans and test cases in a plan (i.e. with a status and a status change history), support:
@@ -180 +180 @@
 '''Since: 1.2.0'''
 
-Custom fields can be added to the four test objects and to the workflow state object, by declaring them in the trac.ini file.
+Custom fields can be added to the four test objects and to the [wiki:TestManagerForTracPluginWorkflow workflow] state object, by declaring them in the trac.ini file.
 See the README.txt file for how to recreate this example.
 The following screenshot shows a custom "platform" field added to the Test Case object, and how it is presented to the User for editing.
@@ -194 +194 @@
 '''Since: 1.2.0'''
 
-The following figure shows a sample workflow added to Test Cases with custom sample operations.
+The following figure shows a sample [wiki:TestManagerForTracPluginWorkflow workflow] added to Test Cases with custom sample operations.
 No built-in operation is currently implemented but the sample one shown here, named 'sample_operation', which logs a debug message with the text input by the User.
 
 Every object which has a workflow defined is created in a "new" state, so every transition should consider this as the first state in the state machine.
 
-This is a sample content of the trac.ini file to associate a workflow toi the Test Case object.
+This is a sample content of the trac.ini file to associate a workflow to the Test Case object.
+[[BR]]
 
 {{{
@@ -210 +211 @@
 sing.operations = sample_operation
 
-calmdown = new -> calm
+calmdown = singing -> calm
 calmdown.permissions = TEST_MODIFY
-calmdown.operations = sample_operation
 
 kill = asleep,calm -> dead
@@ -218 +218 @@
 }}}
 
-See the README.txt file for more details.
-
+[[BR]]
+Refer to the [wiki:TestManagerForTracPluginWorkflow Workflow Engine] description page for more details.
 
 [[BR]]