Changes between Version 31 and Version 32 of TestManagerForTracPlugin
- Timestamp:
- Oct 1, 2010, 3:11:09 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TestManagerForTracPlugin
v31 v32 13 13 14 14 Multiple Test Plans can be associated to any Test Catalog, in order to keep track of the execution of the corresponding Test Cases in a particular testing context. 15 16 A generic, customizable '''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. 15 17 16 18 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), support: 17 19 * '''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. 18 20 * Change history 19 * Listener interface to be notified of object creatio , modification and deletion21 * Listener interface to be notified of object creation, modification and deletion 20 22 * '''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 :-) 21 23 * '''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. … … 25 27 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. 26 28 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. 27 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.29 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. 28 30 29 31 The '''programmatic''' and the '''RESTful API''' are documented in details in this page TestManagerForTracPluginApi. 30 32 31 Here follows an overview of the plugin functionalities. For a full tutorial, refer to the powerpoint presentations attached below (the ones with shorter names work). 33 Here follows an overview of the plugin functionalities. For a brief [wiki:TestManagerForTracPlugin#Tutorialaspowerpointpresentation tutorial], refer to the powerpoint presentations attached below. 34 Note, anyway that the tutorial was developed for release 1.0.0 and so does not cover Test Plans, Workflows and Custom properties. 32 35 33 36 [[BR]] … … 40 43 Notice at the top of the page breadcrumbs to easily navigate up in the catalogs tree. 41 44 42 You can add sub-catalogs or Test Cases simply by entering a name (blanks and case is supported) and click the appropriate button. A new wiki page is generated, with a naming convention allowing the plugin code to position it correctly in the catalogs tree, and opened for editing. 43 Be careful that the first line will always be taken as the title of the catalog (the same stands for test cases, read below). 44 45 Just save the new page ("Submit Changes") and you'll have your new (sub-)catalog in place. 45 You can add sub-catalogs or Test Cases simply by entering a name (blanks and case are supported) and click the appropriate button. A new wiki page is generated, with a naming convention allowing the plugin code to position it correctly in the catalogs tree, and opened for browsing. 46 47 If you wish to edit the title or add some textual contents to the (sub-)catalog, click on "Edit Page" at the bottom of the screen. 48 49 '''Be careful''' that the first line (the one surrounded by '==') will always be taken as the title of the catalog (the same stands for test cases, read below), so do not remove this line. You can edit this line to change the test catalog title, anyway. 50 51 Just save the page ("Submit Changes") to save your textual changes to the (sub-)catalog. 52 53 To '''delete a Test Catalog''' you must delete the corresponding Wiki page. Notice that this operation does not delete all of the Test Cases contained in the Catalog. You must either delete each Test Case individually, or first move them into a different catalog first. 54 55 If you '''mistakenly deleted''' a Test Catalog, you can save the day by recreating a Wiki page with the exact name. To do so, enter the desired name directly in the browser's URL, after the /wiki/ part. Trac will show you an empty page for the catalog, but already populated with all of your existing test cases and sub-catalogs. 56 Click on "Create this page", give it a title (surrounded by '==') and submit your changes. The new (old) catalog is in place. 46 57 47 58 [[BR]] … … 54 65 55 66 They are implemented again as wiki pages, with a naming convention that allows the plugin code to recognize them and treat them appropriately. 67 68 To add Test Cases into a Test Catalog, open the catalog, go to the bottom of the page and enter a name for the new Test Case to be created into the appropriate text box (blanks and case are supported). Then click the button "Add a Test Case". 69 A new wiki page is generated, with a naming convention allowing the plugin code to position it correctly in the catalogs tree, and opened for editing. 70 '''Be careful''' that the first line (the one surrounded by '==') will always be taken as the title of the Test Case, so do not remove this line. You can edit this line to change the test case title, anyway. 71 72 You can then add the Test §Case description just below the first line (i.e. title), using WikiFormatting, adding attachments and everything else is supported for Wiki pages. 73 74 When you are done, save the page ("Submit Changes") to save your new Test Case. 75 76 To '''delete a Test Case''' you must delete the corresponding Wiki page. 56 77 57 78 Again, notice the breadcrumbs at the top, useful to go back to the enclosing catalog or any catalog up the hierarchy.
