Changes between Version 16 and Version 17 of TestManagerForTracPluginApi


Ignore:
Timestamp:
Jan 20, 2011, 5:53:26 PM (4 years ago)
Author:
seccanj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestManagerForTracPluginApi

    v16 v17  
    66There are three main APIs available:
    77
    8  * An [wiki:TestManagerForTracPluginRPCApi '''XML-RPC''' API], allowing you to remotely control your test artifacts using a standard XML-RPC protocol. For example, using the Python {{{xmlrpclib}}} library, you can get test object properties, create objects and so on with as few as two lines of code.
    9  * An [wiki:TestManagerForTracPluginRestfulApi '''HTTP RESTful''' API], allowing you to remotely control your test artifacts by means of simple HTTP GET requests,
    10  * A plain [wiki:TestManagerForTracPluginPythonApi '''Python''' API], allowing for components running in the Trac environment to have a fine-grained control over any artifact, managing their life-cycle, listening to events, reacting to status changes and workflow transitions.
     8 * An '''[wiki:TestManagerForTracPluginRPCApi XML-RPC API]''', allowing you to remotely control your test artifacts using a standard XML-RPC protocol. For example, using the Python {{{xmlrpclib}}} library, you can get test object properties, create objects and so on with as few as two lines of code.
     9 * An '''[wiki:TestManagerForTracPluginRestfulApi HTTP RESTful API]''', allowing you to remotely control your test artifacts by means of simple HTTP GET requests,
     10 * A plain '''[wiki:TestManagerForTracPluginPythonApi Python API]''', allowing for components running in the Trac environment to have a fine-grained control over any artifact, managing their life-cycle, listening to events, reacting to status changes and workflow transitions.
    1111