Changes between Version 51 and Version 52 of TestManagerForTracPlugin


Ignore:
Timestamp:
Jan 4, 2011, 8:05:28 PM (4 years ago)
Author:
seccanj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestManagerForTracPlugin

    v51 v52  
    1818A '''[wiki:TestManagerForTracPluginApi Programmatic API]''' is available to interact with the test management environment both by an HTTP RESTful interface and a Python classes interface.
    1919
    20 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.
     20The plugin has been made modular:
     21
     22 * 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.
     23
     24 * All the data manipulation layer has been extracted into a '''[wiki:TestManagerForTracPluginGenericClass Generic Persistent Class framework]''' plugin, which can be easily used by any other plugin developer to provide persistence, security, change history, custom properties, pattern matching search, and other features to their basic data model with a handful lines of code. 
    2125
    2226All 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:
     
    3135The developed workflow engine is able to work on any Trac Resource, it is not confined to this plugin ones. You can then define a workflow on any Trac resource, including Wiki pages, declaratively in the trac.ini file.
    3236You will then add a handful of custom code (for example in an ITemplateStreamFilter) to add the markup that the workflow engine generates for you to your desired Trac web page.
    33 See the enhancement tickets documentation or the README.txt file contained in the egg (if you don't wish to actually browse the code) for further details.
     37See [wiki:TestManagerForTracPluginWorkflow#Extendworkflowsupporttoanyofyourartifacts this page] for further details.
    3438
    3539The '''programmatic''' and the '''RESTful API''' are documented in details in this page TestManagerForTracPluginApi.
     
    422426[[BR]]
    423427[[BR]]
    424 '''During the last month:'''
    425 [[BR]]
     428'''During the last months:'''
     429[[BR]]
     430
     431'''Release 1.4.1''' (2010-12-27):
     432  o Enhancement #7846 (Track-Hacks): Customizable test case outcomes (aka verdicts)[[BR]]
     433  o Enhancement #7570 (Track-Hacks): Add a relationship table between tickets and test cases in plan, and corresponding API[[BR]]
     434  o Added wiki documentation on the '''[wiki:TestManagerForTracPluginGenericClass Generic Persistent Class framework]'''
    426435
    427436'''Release 1.3.12''' (2010-12-19):