Changes between Version 3 and Version 4 of TestManagerForTracPluginWorkflow


Ignore:
Timestamp:
Oct 9, 2010, 4:43:59 PM (4 years ago)
Author:
seccanj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestManagerForTracPluginWorkflow

    v3 v4  
    220220
    221221Yes! You don't have to do anything to:
    222  * Manage you resource states,
    223  * Handle transitions,
     222 * Manage you resource states
     223 * Handle transitions
    224224 * Manage operations
    225225
    226 all this is automatically procided by the plugin.
     226all this is automatically performed by the plugin.
    227227
    228228So, let's take a look at how the TestManager plugin incorporates this web interface support.
     
    291291 * resource: the actual Trac resource instance object of the workflow.
    292292
    293 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.
    294 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:
    295 
    296 {{{
    297 id = get_string_from_dictionary(key)
    298 res = Resource(realm, id)
    299 }}}
     293Note: [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.
     294This 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:
     295
     296{{{
     297  id = get_string_from_dictionary(key)
     298  res = Resource(realm, id)
     299}}}