TestManager

TestManager is a Trac plugin to create Test Cases, organize them in catalogs, generate Test Plans and track their execution status and outcome.

Differently from other test management plugins for Trac that use Tickets as test case holders, this one uses Wiki pages and an additional proprietary data model to store Test Cases. This allows you to not pollute your ticket lists with something that is not a ticket, and at the same time is powered by the Trac search engine and formatting syntax for Wiki pages.

A set of plugins intercept requests for Wiki pages that are test cases and decorate the page with title, breadcrumbs, tree view, type-ahead search inside the catalogs, test case status semaphore and icons and buttons that allow you to create new test cases, sub-catalogs, copy and paste test cases around different catalogs and change a test case status.

Currently tested on Trac 0.11 and Python 2.5.

What is new in this release:

• Enhancement #9751 (Track-Hacks): Ability to sort catalogs.
• Test Catalogs are now sorted by title in the tree and table views.
• Fixed Ticket #9776 (Track-Hacks): Testplans not visible with latest Agilo Plugin.
• Fixed Ticket #9530 (Track-Hacks): Expand all / Collapse all is not running.
• This only happened with the Agilo plugin installed.
• Fixed Ticket #9754 (Track-Hacks): Setting test result seemingly succeeds with expired login.
• Now operations such as setting a test case status and updating a custom field,
• when failing will display a dialog box with an error message.
• Fixed Ticket #9758 (Track-Hacks): Can't delete Test Case in v1.4.9.

What is new in version 1.4.3:

• New release featuring:
• Test statistics charts
• Multiple test plans
• Customizable test outcomes
• Customizable workflows and workflow actions
• Custom properties in all test objects
• Tree and tabular views
• Internationalization
• Programmatic APIs:
• XML-RPC
• HTTP RESTful
• Python

What is new in version 1.2.0:

• 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), now support:
• Custom properties, which can be declared in the trac.ini file and will be available to the User for change, stored in the database and available to change listeners.
• Change history
• Listener interface to be notified of object creatio, modification and deletion
• Customizable Workflow state machine, declared in the trac.ini file, with the same syntax as for Ticket workflows (I may have reused some existing code here :-)
• Customizable Workflow Operations, via a plugin api so that any component can provide its custom operations to be performed upon any workflow action, as defined in the trac.ini file.
• Workflow also supports a listener API for components interested in state transitions and actions performed
• Workflow states also support custom properties, so to be able to convey additional context information on a workflow state and use it in listeners or directly from the database.
• The 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. You 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. See the enhancement tickets documentation or the README.txt file contained in the egg (if you don't wish to browse the code) for further details.

What is new in version 1.1.1:

• Added test management statistics charting.

Requirements:

• Python
• Trac