Changes between Version 3 and Version 4 of TestManagerForTracPluginWorkflow

Timestamp:

Oct 9, 2010, 2:43:59 PM (14 years ago)

Author:

Roberto Longobardi

Comment:

--

TestManagerForTracPluginWorkflow

@@ -220 +220 @@
 
 Yes! You don't have to do anything to:
- * Manage you resource states, 
- * Handle transitions,
+ * Manage you resource states
+ * Handle transitions
  * Manage operations
 
-all this is automatically procided by the plugin.
+all this is automatically performed by the plugin.
 
 So, let's take a look at how the TestManager plugin incorporates this web interface support.
@@ -291 +291 @@
  * resource: the actual Trac resource instance object of the workflow.
 
-Note: TestManager artifact resources are made so that their resource ID is a string representation of their key properties, in the form of a JSON dictionary.
-This is why you see the following code, where to build a Trac Resource corresponding to a TestManager aretifact, I first build the Resource ID as the string representation of the artifact's key properties, then use it to create the Resource:
-
-{{{
-id = get_string_from_dictionary(key)
-res = Resource(realm, id)
-}}}
+Note: [wiki:TestManagerForTracPlugin TestManager] artifact resources are made so that their resource ID is a string representation of their key properties, in the form of a JSON dictionary.
+This is why you see the following code, where to build a Trac Resource corresponding to a [wiki:TestManagerForTracPlugin TestManager] aretifact, I first build the Resource ID as the string representation of the artifact's key properties, then use it to create the Resource:
+
+{{{
+  id = get_string_from_dictionary(key)
+  res = Resource(realm, id)
+}}}