Changes between Version 107 and Version 108 of TestManagerForTracPlugin


Ignore:
Timestamp:
Jan 3, 2014 10:23:18 PM (8 months ago)
Author:
seccanj
Comment:

Completely rewritten

Legend:

Unmodified
Added
Removed
Modified
  • TestManagerForTracPlugin

    v107 v108  
    11[[PageOutline(2-5,Contents,pullout)]] 
    22 
     3''' [ [wiki:TestManagerForTracPluginChangeHistory Latest changes] | [wiki:TestManagerForTracPluginGallery Image gallery] | [http://www.youtube.com/watch?v=BIi3QMT0rT4 Video tutorial on Youtube] | [wiki:TestManagerForTracPluginQuickSetup Quick setup guide] | [http://sourceforge.net/projects/testman4trac Download] | [http://sourceforge.net/projects/testman4trac/files Source] | [#BugsFeatureRequests Bugs/Feature requests] ]''' 
     4 
    35= Test Manager plugin for Trac - Full test management life-cycle: definition, planning, execution, statistics = 
    4  
    5 Jump to the [http://trac-hacks.org/wiki/TestManagerForTracPlugin#RecentChanges list of the latest changes]. 
    6 and watch the [http://www.youtube.com/watch?v=BIi3QMT0rT4 Video tutorial on Youtube], helping old and new users familiarize with the changes and highlighting the recent features of new releases. 
    7  
    8 '''Follow this [wiki:TestManagerForTracPluginQuickSetup Quick setup guide]''' to get you going quickly. 
    9  
    10 '''Note:''' !TestManager release 1.4.8 introduces a new more robust upgrade mechanism.[[BR]][[BR]] 
    11 Unfortunately '''upgrade to 1.4.8 or up is supported only from release 1.4.7 or later'''. If you have an older version than 1.4.7, first upgrade to 1.4.7 and then you can upgrade to the latest version.[[BR]][[BR]] 
    12  
    13 '''Note:''' !TestManager release 1.4.3 requires XmlRpcPlugin to run. I've removed this hard dependency with 1.4.4. Anyway, if you have XmlRpcPlugin you can use the [wiki:TestManagerForTracPluginRPCApi Test Manager remote API]. 
    14  
    15 == Description == 
    16  
    17 This test management Trac plugin can be used to create '''[wiki:TestManagerForTracPlugin#TestCases Test Cases]''', organize them in '''[wiki:TestManagerForTracPlugin#TestCatalogs Catalogs]''', generate '''[wiki:TestManagerForTracPlugin#TestPlans Test Plans]''' and track their execution status and outcome. 
    18  
    19 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. 
    20 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. 
    21  
    22 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. 
    23  
    24 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. 
    25  
    26 A '''[wiki:TestManagerForTracPluginApi Programmatic API]''' is available to interact with the test management environment with three types of interfaces:  
    27  * '''[wiki:TestManagerForTracPluginRPCApi XML-RPC]''',  
    28  * '''[wiki:TestManagerForTracPluginRestfulApi HTTP RESTful]''' and  
    29  * '''[wiki:TestManagerForTracPluginPythonApi Python classes]'''.  
    30  
    31 The plugin has been made modular: 
     6[[Image(Carousel.png, link=)]] 
     7 
     8== Summary == 
     9This test management Trac plugin can be used to create '''[wiki:TestManagerForTracPlugin#TestCases Test Cases]''', organize them in [wiki:TestManagerForTracPlugin#TestCatalogs Catalogs] and generate '''[wiki:TestManagerForTracPlugin#TestPlans Test Plans]''' to track their execution status and outcome. 
     10 
     11Differently 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. 
     12 
     13A set of plugins intercept requests for Wiki pages that match the Test Manager URL namespace and decorate them with additional information stored in the database. 
     14 
     15Features include: 
     16 
     17 * '''Defining test cases and organize in test catalogs (test suites)'''. 
     18 * Defining a hierarchy of catalogs and sub-catalogs, whatever deep. Specifying the exact order of the test cases in any particular test catalog. 
     19 * Test case and catalogs '''versioning''' and history of changes. 
     20 * Test cases and catalogs support Wiki formatting and attachments. 
     21 * Copy/move individual or a set of test cases among catalogs, or organize the catalogs contents easily using drag and drop. 
     22 * '''Defining one or more test plans (test rounds) '''for each test (sub-)catalog, based on all or a portion of the test cases in a (sub-)catalog. Specifying whether the textual contents of the test cases in a plan should be freezed at the current version, or will always be linked to the latest version. 
     23 * '''One-click changing status of a test case''' - i.e. marking a test case in a particular test plan as successful or failed. 
     24 * '''Ticket integration''': opening tickets directly from a (usually failed) test case, keeping track of the relationship. Navigating from a test case to its related tickets and vice-versa. 
     25 * Test cases, catalogs and plans can have their own '''custom properties''', defined in trac.ini like tickets. All property types are supported: text, text area, listbox, radio buttons, checkbox. 
     26 * Defining '''custom test outcomes (statuses)''', in addition to the built-in "Untested", "Success", "Failed". 
     27 * Test execution '''statistical charts''', showing the overall testing activity, status of the test plans, statistics on the tickets opened agains all or a specific test plan. '''Exporting the data to CSV'''. 
     28 * Choosing between Tree and Tabular view of the test catalogs or test plans, and the contained test cases. 
     29 * In the tabular view, choosing which columns to display, including any custom property, and the ability to add '''calculated rows''', such as sums, averages, min or max. 
     30 * Type-ahead searching and filtering from the tree and tabular view. 
     31 * Breadcrumbs to easily navigate through test catalogs and plans. 
     32 * Integration with Trac search engine. 
     33 * '''Fine-grained security''' with six new Trac permissions. 
     34 * Administration panels to easily configure the test manager's behavior. 
     35 * Creating '''templates for test cases and test catalogs'''. Specifying which default template should be used for test cases in any particular catalog. 
     36 * '''Importing/exporting''' test cases and test plans from/to Excel in CSV format. 
     37 * National Language Support (NLS) and currently translated into '''Italian, French, German, Spanish, Russian and Korean'''. 
     38 * '''Remote APIs: XML-RPC, RESTful.''' 
     39 * Internal Python API. 
     40 
     41A '''[wiki:TestManagerForTracPluginApi Programmatic API]''' is available to interact with the test management environment with three types of interfaces: 
     42 
     43 * '''[wiki:TestManagerForTracPluginRPCApi XML-RPC]''', 
     44 * '''[wiki:TestManagerForTracPluginRestfulApi HTTP RESTful]''' and 
     45 * '''[wiki:TestManagerForTracPluginPythonApi Python classes]'''. 
     46 
     47The '''APIs''' are documented in details in this page: TestManagerForTracPluginApi. 
     48 
     49'''Trac plugin developers''' may be interested to the plugin reusable modular architecture: 
    3250 
    3351 * 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. 
    3452 
    35  * 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.   
    36  
    37 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: 
    38  * '''[http://trac-hacks.org/wiki/TestManagerForTracPlugin#Customfields 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. 
    39  * Change history 
    40  * Listener interface to be notified of object creation, modification and deletion 
    41  * '''[http://trac-hacks.org/wiki/TestManagerForTracPluginWorkflow 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 :-) 
    42  * '''[http://trac-hacks.org/wiki/TestManagerForTracPluginWorkflow#Howtoprovidecustomoperations 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. 
    43  * Workflow also supports a listener API for components interested in state transitions and actions performed 
    44  * 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. 
    45  
    46 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. 
    47 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. 
    48 See [wiki:TestManagerForTracPluginWorkflow#Extendworkflowsupporttoanyofyourartifacts this page] for further details. 
    49  
    50 The '''programmatic''' and the '''RESTful API''' are documented in details in this page TestManagerForTracPluginApi. 
    51  
    52 Here follows an overview of the plugin functionalities. For a brief [wiki:TestManagerForTracPlugin#Tutorialaspowerpointpresentation tutorial], refer to the powerpoint presentations attached below.  
    53 Note, anyway that the tutorial was developed for release 1.0.0 and so does not cover Test Plans, Workflows and Custom properties. 
    54  
    55 [[BR]] 
    56 [[BR]] 
     53 * 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. 
     54 
     55 * 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: 
     56   * '''[#Customfields 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. 
     57   * Property and status change history 
     58   * Listener interface to be notified of object creation, modification and deletion 
     59   * '''[TestManagerForTracPluginWorkflow 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 :-) 
     60   * '''[TestManagerForTracPluginWorkflow#Howtoprovidecustomoperations 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. 
     61   * Workflow also supports a listener API for components interested in state transitions and actions performed 
     62   * 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. 
     63 
     64 * 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 [wiki:TestManagerForTracPluginWorkflow#Extendworkflowsupporttoanyofyourartifacts this page] for further details. 
     65 
     66Here follows an overview of the plugin functionalities. For a brief [#Tutorialaspowerpointpresentation tutorial], refer to the [http://www.youtube.com/watch?v=BIi3QMT0rT4 Video tutorial on Youtube]. 
     67 
    5768== Test Catalogs == 
    58 Test catalogs contain sub-catalogs or Test Cases. A Javascript tree view displays a catalog node and its sub-tree, including all of the test cases contained. 
    59  
    60 Next to each catalog (or sub-catalog) a number in brackets shows the number of test cases it contains. 
    61  
    62 Notice at the top of the page breadcrumbs to easily navigate up in the catalogs tree. 
    63  
    64 You can '''choose between a tree-like and a tabular representation''' of the catalog and all of its contained sub-catalogs and test cases, as shown in  
    65 The former is useful to actually work on the Test Catalog, adding sub-catalogs and new test cases, or modifying them. 
    66 The latter, which also reports a printout of all the Test Case descriptions, may be useful for a Test Engineer to save or print as a handout to actually run the test cases in the catalog. 
    67  
    68 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. 
    69  
    70 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. 
    71  
    72 '''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. 
    73  
    74 Just save the page ("Submit Changes") to save your textual changes to the (sub-)catalog. 
    75  
    76 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. 
    77  
    78 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. 
    79 Click on "Create this page", give it a title (surrounded by '==') and submit your changes. The new (old) catalog is in place. 
    80  
    81 [[BR]] 
    82 [[BR]] 
    83 [[Image(screen2.JPG)]] 
    84 [[BR]] 
    85 '''Tree View of the Test Catalog''' 
    86 [[BR]] 
    87 [[BR]] 
    88 [[Image(screen13.png)]] 
    89 [[BR]] 
    90 '''Tabular view of the Test Catalog''' 
    91 [[BR]] 
    92 [[BR]] 
     69Test Catalogs contain Test Cases and may organize them in sub-catalogs. 
     70 
     71They are implemented as wiki pages, with a naming convention that allows the plugin code to recognize them and treat them appropriately, and with a set of auxiliary database tables. This provides out-of the box support for rich text formatting (using Wiki syntax), attachments and versioning. 
     72 
     73This also means that the `WIKI_VIEW`, in addition to the `TEST_WIEW`, permission is required to be able to browse test catalogs and test cases. 
     74 
     75You can '''choose between a tree-like and a tabular representation''' of the catalog and all of its contained sub-catalogs and test cases, as shown in the following figures. 
     76 
     77To switch between the two view types, click on the corresponding icons at the top-left corner. To change the default view type, i.e. tree or table, use the Test Manager '''Settings''' administration panel. 
     78 
     79On a Test Catalog page, from the top down, you have: 
     80 
     81 * Some '''breadcrumbs''', to easily locate where the current catalog is and to navigate up in the catalogs tree. 
     82 * '''Switch to Tabular View''' / '''Switch to Tree View''' icons. Use these icons to switch between the tree vew and the tabular view. The former is useful to actually work on the Test Catalog, adding sub-catalogs and new test cases, or modifying them. The latter, which also reports a printout of all the Test Case descriptions, may be useful for a Test Engineer to save or print as a handout to actually run the test cases in the catalog. This is particularly true for [#TestPlans Test Plans]. The tabular view is also the only one to show all of the [#Customfields Custom Fields] you may have added to the catalogs, plans or test cases. 
     83 * The catalog's '''Title'''. This is the text you have entered in the parent catalog's '''New Sub-Catalog''' text field when you created this catalog. 
     84 * '''Filter''' text box. Type inside the text box to filter all sub-catalogs and test cases matching your input text. See [#SearchingandfilteringTestCases Searching and filtering Test Cases] for details. 
     85 * '''Expand All''' and '''Collapse All'''. In tree view mode, use these links to expand or collapse all the tree nodes. 
     86 * '''Sub-catalogs and Test Cases'''. You can '''browse''' each sub-catalog and test case by following the corresponding link. Hovering on a Test Case, a pencil icon will appear on the right. Click on it to go to the Test Case directly into '''Edit''' mode. 
     87 * '''Custom fields'''. If you have defined any custom fields for the Test Catalog artifact, they appear here. You can then view and edit their values directly from this page. See [#Customfields Custom Fields] for details. 
     88 * '''New Sub-Catalog''' text field and button. You can add sub-catalogs simply by entering a name (blanks, special characters and case are supported) and clicking the corresponding 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. 
     89 * '''New Test Case''' text field and button. You can add a new Test Case inside the currently displayed catalog by entering a name and clicking the corresponding button. As for a new catalog, a new wiki page is generated, but it is now opened for editing. '''Be careful''' that the first line (the one surrounded by '==') will always be taken as the title of the test case (the same stands for test catalogs), so do not remove this line. You can edit this line to change the test case title, anyway. 
     90 * '''Generate a new Test Plan''' button. Allows you to generate a new test execution plan for the Test Cases contained in this catalog. See [#TestPlans Test Plans] for details. 
     91 * '''Select Multiple Test Cases''' button. It will display checkboxes next to the test cases in the catalog (and su-catalogs). You may then select one or more test cases to perform operations on them. See [#MovingorCopyingTestCasesfromonecatalogtoanother Moving or Copying Test Cases from one catalog to another] for details. 
     92 * '''Copy the Selected Test Cases''' button. You can copy (into a "virtual" clipboard) the test cases you have selected (see previous item), to be eventually pasted into some other (or the same) catalog, or sub-catalog. 
     93 * '''Paste the copied Test Cases here''' button. This button, only visible if you have previously copied some test cases into the "virtual" clipboard, allows you to paste them into the current Test Catalog. 
     94 * '''Move the copied Test Case here''' button. This button, only visible if you have previously cut a single test case into the "virtual" clipboard, allows you to paste them into the current Test Catalog. 
     95 * '''Import Test Cases''' button. Allows you to import a seto of test cases into this catalog from a CSV file. See [#ImportingTestCasesfromaCSVfileintoaTestCatalog Importing Test Cases from a CSV file into a Test Catalog] for details. 
     96 * '''Export Test Catalog''' button. Allows you to export the Test Catalog, including sub-catalogs and all the contained test cases, to CSV format. See [#ExportingTestCatalogsorTestPlansintoCSVfile Exporting Test Catalogs or Test Plans into CSV file] for details. 
     97 * '''Organize Test Catalogs''' button. It will display a dialog box where you can, using simple drag and drop, reorganize the test cases in this catalog and sub-catalogs. See [#OrganizingthecontentsofaTestCatalog Organizing the contents of a Test Catalog] for details. 
     98 * '''Available Test Plans''' section. The number in brackets shows the number of [#TestPlans Test Plans] that have been generated for this catalog. Expand the section to access detailed test plan information and to navigate to the individual test plans. Type inside the text box to filter all test plan information matching your input text. 
     99 * '''Object Change History''' section. In addition to the standard Wiki versioning, test objects support their own change history, which lets you inspect who changes which property and when, also showing its old and new value. This is also particularly useful for [#Customfields Custom Fields] you may add to the test objects. See [#TestArtifactChangeHistory Test Artifact Change History] for more details. 
     100 * '''Edit this page''' button. If you wish to edit the title of the catalog or add some textual contents to it, click on this button to enter the Wiki page editing mode. Be careful that the first line is always interpreted as the test catalog title. You can then add the Test Catalog description just below it, using WikiFormatting, adding attachments and everything else is supported for Wiki pages. When you're done, simply save the page with '''Submit Changes''' to save your textual changes to the catalog. 
     101 * '''Attach File''' button. Use this button to attach files to the Catalog page. 
     102 * '''Rename page''' button. This function is '''not allowed''' for Test Catalogs, Test Cases or Test Plans. This because the Test Manager plugin uses the page names to keep track of the test artifacts hierarchy information. Submitting a new page name will then throw you a meaningful error. '''To change the Catalog's title''', use the '''Edit this page''' button and change the first text line. It is interpreted as the catalog title. If you '''wish to move '''the object elsewhere, instead, use the 'move' Test Manager functions. 
     103 * '''Delete this version''' button. It will delete the current Test Catalog's '''description Wiki page''', and revert to the last one. This action will have no effect on the changes you may have done to the sub-catalogs or test cases contained within. To undo changes to the Wiki pages of any of these latter objects, go to the corresponding page and work with the Wiki versions accordingly. As long as the Test Catalog internal organization in sub-catalogs and Test Case, Test Manager does not have a "Test Catalog snapshot" kind of functionality, which you may revert to. 
     104 * '''Delete Test Catalog''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the current Test Catalog, all the contained sub-catalogs, Test Cases, Test Plans and the status history of them. '''''Caution''''': there in no undo functionality here. 
     105 
     106|| [[Image(TestCatalog01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TreeviewoftheTestCatalog])]] || [[Image(TestCatalog04.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TabularviewoftheTestCatalog])]] || 
     107|| '''Tree view of the Test Catalog''' || '''Tabular view of the Test Catalog''' || 
     108 
     109=== Searching and filtering Test Cases === 
     110A type-ahead, browser-side filtering feature allows for easily locating Test Cases matching a particular naming convention in the title, and/or a particular execution status. 
     111 
     112This is available both in the context of a Test Catalog and in Test Plans. 
     113 
     114Multiple words (or parts of) separated by blanks are supported, in AND condition. 
     115 
     116In the case of a [#TestPlans Test Plan], you can also filter by test case status. The default statuses are (even substrings of) the following, but you can use [#CustomTestCaseOutcomesi.e.statesverdicts Custom Test Case Outcomes (i.e. states, verdicts)] as well: 
     117 
     118 * untested 
     119 * successful 
     120 * failed 
     121 
     122[[BR]] [[Image(TestCatalog05.png_th.png, link=[wiki:TestManagerForTracPluginGallery#FilteringtheTestCasesinacatalogtabularview])]] 
     123 
     124'''Filtering the Test Cases in a catalog tabular view'''[[BR]] 
     125 
     126== Test Cases == 
     127Test Cases are the smallest units of test execution. 
     128 
     129They are implemented again as wiki pages, with a naming convention that allows the plugin code to recognize them and treat them appropriately, and with a set of auxiliary database tables. This provides out-of the box support for rich text formatting (using Wiki syntax), attachments and versioning. 
     130 
     131To 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, special characters and case are supported). Then click the button '''Add a Test Case'''.  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. '''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, at any time. 
     132 
     133You can then add the Test Case description just below the first line (i.e. the title), using WikiFormatting, adding attachments and everything else is supported for Wiki pages. 
     134 
     135When you are done, save the page '''Submit Changes''' to save your new Test Case. 
     136 
     137A Test Case is created in the context of a Test Catalog. Think of it as the '''Test Case''' "class", or "definition". It does not carry iformation about whether the Test Case was executed or when, and wheter it succeded or failed. 
     138 
     139To plan a test execution session, you will then generate a [#TestPlans Test Plan]. A Test Plan is used to record a specific execution of a set of Test Cases. Thus, a Test Cases also exists in the context of one or more Test Plans. Think of those as Test Case "instances", or "uses". In the context of the Test Manager plugin, these are called '''Test Cases in a Plan'''. 
     140 
     141A '''Test Case in a Plan, in addition to a basic Test Case''', also records the execution outcomes (or verdicts), i.e. whether a particular execution of the Test Case in the context of the containing Test Plan was successful or failing. You can also see the complete test status change history at the bottom of the Test Case in Plan page. 
     142 
     143On a Test Case page, from the top down, you have: 
     144 
     145 * Some '''breadcrumbs''', to easily locate where the current test case is and to navigate up in the catalogs tree, or to the containing Test Plan. 
     146 * The Test Case's '''Title'''. This is the text you have entered in the parent catalog's '''New Test Case''' text field when you created this Test Case. 
     147 * Test Case '''description text'''. This is the main test case contents, probably describing the test preconditions, the steps to be perfomed to run the test case and the expected results. You can edit these contents using the '''Edit this page''' button. See below. 
     148 * '''Custom fields'''. If you have defined any custom fields for the "Test Case" or "Test Case in a Plan" artifacts, they appear here. You can then view and edit their values directly from this page. See [#Customfields Custom Fields] for details. 
     149 * '''Open a Ticket on this Test Case''' button. Allows you to open a ticket that will be related to this test case. If you are browsing a Test Case definition, the ticket will not be related to any particular Test plan. If, instead, you are browsing a Test Case in (the context of) a Plan, the ticket will be related to the execution of th Test Case in that particular Test Plan. See [#LinkingaTickettoaTestCase Linking a Ticket to a Test Case] for details. 
     150 * '''Show Related Tickets''' button. Clicking this button will perform a custom query listing all the Tickets related to this Test Case and, if applicable, the containing Test plan. 
     151 * '''Move the Test Case into another catalog''' button. Only available on Test Case definitions. It allows you to cut (into a "virtual" clipboard) the test case, to be eventually pasted into some other (or the same) catalog, or sub-catalog. Push the button, then navigate to the destination catalog and puch the '''Move the copied Test Case here''' button to complete the move operation. Also look at the '''Organize Test Catalogs''' functionality for an alternative way of moving Test Cases. Refer to [#TestCatalogs Test Catalogs] for details. 
     152 * '''Duplicate the Test Case''' button. Only available on Test Case definitions. Lets you make an exact copy of this Test Case definition. Note that the test execution statuses (i.e. successful, failed, etc...) associated to the original Test Cases in any Test Plan are not duplicated along with the Test Case definition. 
     153 * '''Add to a Test Plan''' button. Only available on Test Case definitions. Allows you to add the Test Case to one or more suitable Test Plans, i.e. Test Plans that have been defined as not containing all the test cases (current and future) of the associated Test Catalog, but only a selected set of them. 
     154 * '''Object Change History''' section. In addition to the standard Wiki versioning, test objects support their own change history, which lets you inspect who changes which property and when, also showing its old and new value. This is also particularly useful for [#Customfields Custom Fields] you may add to the test objects. See [#TestArtifactChangeHistory Test Artifact Change History] for more details. 
     155 * '''Edit this page''' button. If you wish to edit the title of the Test Case or edite the textual contents of it, click on this button to enter the Wiki page editing mode. When you're done, simply save the page with '''Submit Changes''' to save your textual changes to the test case. '''Be careful''' that the first line is always interpreted as the test case title. 
     156 * '''Attach File''' button. Use this button to attach files to the Test Case page. 
     157 * '''Rename page''' button. This function is '''not allowed''' for Test Catalogs, Test Cases or Test Plans. This because the Test Manager plugin uses the page names to keep track of the test artifacts hierarchy information. Submitting a new page name will then throw you a meaningful error. '''To change the Test Case's title''', use the '''Edit this page''' button and change the first text line. It is interpreted as the test case title. If you '''wish to move '''the object elsewhere, instead, use the 'move' Test Manager functions. 
     158 * '''Delete this version''' button. It will delete the current Test Case's '''description Wiki page''', and revert to the last one. 
     159 * '''Delete page''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the current Test Case definition and all of the Test Case instances in any Test Plan, including their status change history. '''''Caution''''': there in no undo functionality here. 
     160 
     161|| [[Image(TestCase01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#SampleTestCase])]] || [[Image(TestCase02.png_th.png, link=[wiki:TestManagerForTracPluginGallery#LateaddingaTestCasetooneormoreTestPlans])]] || 
     162|| '''Sample Test Case''' || '''Late adding a Test Case to one or more Test Plans''' || 
     163 
     164== Test Plans == 
     165'''Since: 1.1.0''' 
     166 
     167A '''Test Plan''' represents a plan for a particular execution of all the Test Cases in a Test Catalog (or sub-catalog). 
     168 
     169Think for example at the build verification test following a nightly build, or, for traditional projects, Functional Test and eventually Customer Verification Test. 
     170 
     171Thus a Test Plan is associated to one Test Catalog, or sub-catalog. You can have any number of Test Plans for one Test Catalog, anyway. The list of Test Plans you generated for a Test Catalog is displayed in a table at the bottom of the same catalog, as shown in the following figure. 
     172 
     173The Test Cases associated to a Test Plan are called '''Test Cases in a Plan'''. Refer to [#TestCases Test Cases] for details about the additional information carried by these particular artifacts. 
     174 
     175[[BR]] '''To create a Test Plan for a catalog''', open the desired Test Catalog (or sub-catalog), enter the name of the new Test Plan in the appropriate text field and click '''Generate a new Test Plan'''. A dialog box will be displayed, as show in the next figure, which lets you choose the characteristics of the Test Plan. 
     176 
     177Available options are: 
     178 
     179 * Whether the new Test Plan will contain all the Test Cases in the catalog, or only the ones previously selected (see [#TestCatalogs Test Catalogs] for an explaination about how to select multiple test cases in a catalog. 
     180 * Whether the textual contents of the test cases in the new plan should be freezed at their current version, or will always be linked to the latest version. In fact, some time after the test plan has been executed it may be desired, for auditing purposes, to be able to view the exact contents of the test case description ''at the time the test plan was generated'', disregarding all the changes that may have occurred later. 
     181 
     182The new Test Plan will be opened for display, showing all of the Test Cases in the catalog, in the "Untested" status. 
     183 
     184As with Test Catalogs, you can '''choose between tree and a tabular representation''' of the Test Plan, as shown in the figures below. 
     185 
     186 * The former is useful to actually work on the Test Plan and to view test cases before actually going and executing them. It also gives you a bird-eye view of the test execution progress and results. Additionally, you can set a test case verdict directly form the tree view, left-clicking on any Test Case's traffic light and changing its color using the pop-up menu that comes out. 
     187 * The latter, which indicates for each Test Case the latest status modification and its author, may be useful to keep as the documentation of a just run test plan. It is also the only way to display the Test Case in a Plan [#Customfields Custom Fields] you may have set. Additionally, you can set a test case verdict directly form the table view, left-clicking on any Test Case's traffic light and changing its color using the pop-up menu that comes out. 
     188 
     189On a Test Plan page, from the top down, you have: 
     190 
     191 * '''Back to the Catalog''' link. It allows you to navigate back to the Test Catalog associated to this plan. 
     192 * The Test Plan's '''Title'''. This is the text you have entered in the parent catalog's '''Generate a new Test Plan''' text field when you created this Test Plan. 
     193 * Test Plan '''properties'''. The author, creation time and basic characteristics of the Test Plan are displayed here. 
     194 * '''Test Catalog title'''. The associated Test Catalog title is reported here. 
     195 * '''Filter''' text box. Type inside the text box to filter all sub-catalogs and test cases matching your input text. In the context of a Test Plan you can also filter by the test execution status. See [#SearchingandfilteringTestCases Searching and filtering Test Cases] for details. 
     196 * '''Expand All''' and '''Collapse All'''. In tree view mode, use these links to expand or collapse all the tree nodes. 
     197 * '''Sub-catalogs and Test Cases'''. 
     198   * A traffic light icon on a sub-catalog indicates the '''worse outcome''' of all the contained test cases. Red is considered worse than yellow, which is considered worse than green. 
     199   * You can '''browse''' each sub-catalog and '''Test Case instance''' by following the corresponding link. 
     200   * Hovering on a Test Case, a pencil icon will appear on the right. Click on it to go to the '''Test Case definition''' directly into '''Edit''' mode. Refer to [#TestCases Test Cases] for an explaination of the difference between Test Case definition and instance. 
     201   * You can '''set a test case verdict''' directly from the tree or tabular view, left-clicking on any Test Case's traffic light and changing its color using the pop-up menu that comes out. If the basic three outcomes do not fit your needs, see [#CustomTestCaseOutcomesi.e.statesverdicts Custom Test Case Outcomes (i.e. states, verdicts)] for an explaination about how to augment them. 
     202 * '''Custom fields'''. If you have defined any custom fields for the "Test Case" or "Test Case in a Plan" artifacts, they appear here. You can then view and edit their values directly from this page. See [#Customfields Custom Fields] for details. 
     203 * '''Export Test Plan''' button. Allows you to export the Test Plan to CSV format. See [#ExportingTestCatalogsorTestPlansintoCSVfile Custom Test Case Outcomes (i.e. states, verdicts)] for details. 
     204 * '''Clone Test Plan''' button. This button will open a dialog where you can specify a name for the cloned Test Plan. The cloned Test Plan will inherit all the characteristics of the original one, but the contained Test Cases will '''all be reset to Untested''', and their test status change history emptied. 
     205 * '''Object Change History''' section. In addition to the standard Wiki versioning, test objects support their own change history, which lets you inspect who changes which property and when, also showing its old and new value. This is also particularly useful for [#Customfields Custom Fields] you may add to the test objects. See [#TestArtifactChangeHistory Test Artifact Change History] for more details. 
     206 * '''Edit this page''' button. This button allows you to edit the Wiki page that contains '''the associated Test Catalog description'''. A Test Plan does not have itself a specific Wiki page. If you need to record specific Test Plan information, you may want to use a [#Customfields Custom Field], possibly of type textarea. Refer to [#TestCatalogs Test Catalogs] for details about editing their descriptions. 
     207 * '''Attach File''' button. Use this button to attach files to the associated Test Catalog wiki page. There is currently no way to attach files to a specific Test Plan. 
     208 * '''Rename page''' button. This function is '''not allowed''' for Test Catalogs, Test Cases or Test Plans. This because the Test Manager plugin uses the page names to keep track of the test artifacts hierarchy information. Submitting a new page name will then throw you a meaningful error. 
     209 * '''Delete this version''' button. It will delete the associated Test Catalog's description Wiki page, and revert to the last one. 
     210 * '''Delete page''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the associated Test Catalog. Refer to [#TestCatalogs Test Catalogs] for details about what will be actually deleted. '''''Caution''''': there in no undo functionality here. 
     211 
     212You have two ways of setting the execution outcome of a Test Case in a particular Test Plan (see figures below): 
     213 
     214 1. Directly from the test plan tree or tabular view, by clicking on the traffic-light icon and choosing the new color from the menu that opens. (Since 1.4.7) 
     215 1. By opening the test case first, by clicking on its name in the Test Plan tree or table, and then clicking on the corresponding traffic-light at the bottom of the page. 
     216 
     217You don't need to save anything, the changes are immediately recorded into the database and reflected in the Test Plan. 
     218 
     219|| [[Image(TestCatalog02.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TheNewTestPlandialog])]] || [[Image(TestPlan01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TreeviewofaTestPlan])]] || [[Image(TestPlan03.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TabularviewofaTestPlan])]] || 
     220|| '''The New Test Plan dialog''' || '''Tree view of a Test Plan''' || '''Tabular view of a Test Plan''' || 
     221 
     222== Moving or Copying Test Cases from one catalog to another == 
     223It is also possible to move a single Test Case, or copy multiple Test Cases into a different catalog, with an experience similar to cut&paste. 
     224 
     225As an alternative, it is also possible to ![OrganizingthecontentsofaTestCatalog graphically organize the contents of a Test Catalog] using drag&drop. 
     226 
     227=== Moving a single Test Case === 
     228To move a single Test Case from one catalog into a nother, you: 
     229 
     230 1. Open the Test Case 
     231 1. Click on the "Move the Test Case into another catalog" button. This is similar to a "cut" operation, but into a "virtual" clipboard. 
     232 1. Navigate and open the destination catalog 
     233 1. Click on "Move the copied Test Case here" button (which only appears if a Test Case has been cut first). 
     234 
     235It is also possible to cancel the operation at any time by clicking the "Cancel" button in the yellow message at the top of the page. 
     236 
     237=== Copying multiple Test Cases === 
     238To copy one or more Test Cases, even from different catalogs, and paste them all together into a destination (sub-)catalog, you: 
     239 
     240 1. Open the Catalog. Expand the tree nodes as you like. 
     241 1. Click on the "Select Multiple Test Cases" button. A checkbox appears next to every Test Case in the catalog and the sub-catalogs. See the next figure. 
     242 1. Select the Test Cases you wish to copy into another catalog. 
     243 1. Click on the "Copy the Selected Test Cases" button. This is similar to the usual "Copy" operation, but into a "virtual" clipboard. 
     244 1. Navigate and open the destination catalog, or create a new one. 
     245 1. Click on "Paste the copied Test Cases here" button (which only appears if Test Cases have been copied first). 
     246 
     247Note that the test execution statuses (i.e. successful, failed, etc...) associated to the original Test Cases in any Test Plan are not copied along with the Test Case definitions. 
     248 
     249=== Organizing the contents of a Test Catalog === 
     250To (re-)organize the contents of a Test Catalog, i.e. moving test cases around and changing their intended execution order, you can click the '''Organize Test Catalogs''' button. The dialog shown in the following figure will pop-up. 
     251 
     252Use '''drag and drop''' to move test cases into different catalogs or changing their order. As long as the '''Sort a test plan's test cases''' option in the Test Manager's '''Settings''' panel is set to '''User Specified''', the test cases will be displayed in the specified order when browsing the catalog and any associated test plans. 
     253 
     254''Currently, you can only move Test Cases but not Test Catalogs. In addition to that, copying is not supported yet.'' 
     255 
     256Click '''Save''' to submit your changes. 
     257 
     258[[Image(TestCatalog06.png_th.png, link=[wiki:TestManagerForTracPluginGallery#OrganizeTestCatalogsdialog])]] 
     259 
     260'''Organize Test Catalogs dialog''' 
     261 
     262== Linking a Ticket to a Test Case == 
     263When viewing a Test Case definition or Test Case in a Plan, you can open a new Ticket by means of the '''Open Ticket on this Test Case''' button. 
     264 
     265The new ticket will contain a link back to the corresponding Test Case and, if you were viewing it in the context of a particular Test Plan, of the Test Plan as well. 
     266 
     267The association is particularly useful when browsing the [#TestManagementandExecutionStatistics Test Management and Execution Statistics]. 
     268 
     269This plugin also supports the TracTicketTemplatePlugin to fill a ticket template with this information. In this case, you can use the following parameters in the target ticket template to receive the information: 
     270 
     271 * testCaseNumber: The wiki page for the corresponding Test Case 
     272 * planId: The ID of the Test Plan 
     273 * planName: The name of the Test Plan 
     274 
     275For example, to get the test case number, you template will have something like: 
     276 
     277{{{ 
     278  some template text 
     279  Test Case: %(testCaseNumber)s 
     280  some template text 
     281}}} 
     282=== Showing Tickets related to a Test Case === 
     283While browsing a Test Case, either inside or outside of a Test Plan, you can list all of its related Tickets - i.e. the Tickets that were opened using the above '''Open a Ticket on this Test Case''' button. 
     284 
     285To do this, just browse the Test Case and '''click on the Show Related Tickets button'''. 
     286 
     287If you are browsing a Test Case "definition", i.e. from a Test Catalog, you will be shown all of the Tickets opened against the Test Case '''in any Test Plan'''. 
     288 
     289If you are instead browsing a Test Case in a specific Test Plan, you will be shown all of the Tickets opened against the Test Case '''in that specific Test Plan'''. 
     290 
     291See the following figure for what happens when you click on the "Show Related Tickets" button from the Test Case shown at the previous section. 
     292 
     293Trac plugin developers may be insterested in the fact that a '''[wiki:TestManagerForTracPluginApi#GettingalltheTicketsrelatedtoaTestCase programmatic Python API]''' is provided to retrieve all of the Tickets opened against a Test Case, in all or in a specific Test Plan. 
     294 
     295[[BR]] [[Image(TestCaseInPlan03.png_th.png, link=[wiki:TestManagerForTracPluginGallery#DisplayingtheticketsrelatedtoaTestCaseinaPlan])]] 
     296 
     297'''Displaying the tickets related to a Test Case in a Plan'''[[BR]] [[BR]] 
     298 
     299== Test Management and Execution Statistics == 
     300'''Since: 1.1.1''' 
     301 
     302Charting capabilities allow for tracking the evolution of the test suites, the corresponding test plans and tickets opened against test cases. 
     303 
     304To access the test management statistics, click on '''Test Stats''' in the Trac toolbar on the upper right corner of the page. 
     305 
     306As shown in the next figure, a chart will be displayed with statistics about all the test cases in the system and a default period of time, with more charts available in the other tabs. 
     307 
     308The data can be exported to Excel (CSV format) by means of the links at the bottom of each chart. 
     309 
     310If you select a specific period of time and a specific test plan, you can save the settings by saving (in the favorites, bookmarks, etc.) the URL displayed at the bottom of each chart. 
     311 
     312There are three charts available: 
     313 
     314=== Test activity trend chart === 
     315Displays the number of test cases created during time and the trend of the test activity, in terms of test cases to be tested, successful and failed. 
     316 
     317By means of the filtering criteria at the bottom of the chart, you can select the desired period of time, the chart resolution (in terms of time between different samples) and the Test Plan for your chart. 
     318 
     319You can bookmark the URL named "Static URL" at the bottom of the page in order to go directly with the current selected filtering criteria. 
     320 
     321[[BR]][[BR]][[Image(TestStats01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#Testactivitytrendchart])]] 
     322 
     323'''Test activity trend chart''' [[BR]] 
     324 
     325=== Current test status chart === 
     326Shows the current status of the test activity for all test plans of a specific plan, displaying the number of tests that are successful, failed and yet to be tested. 
     327 
     328[[BR]][[BR]][[Image(TestStats02.png_th.png, link=[wiki:TestManagerForTracPluginGallery#Currentteststatuschart])]] 
     329 
     330'''Current test status chart''' [[BR]] 
     331 
     332=== Tickets trend chart === 
     333As long as [wiki:TestManagerForTracPlugin#LinkingaTickettoaTestCase tickets have been opened from the context of a test case in a plan], by means of the appropriate '''Open a ticket on this test case''' button, this chart shows the trend in tickets associated with all test plans or a specific plan, displaying the number of total, active (i.e. not closed) and closed tickets. 
     334 
     335[[BR]][[BR]][[Image(TestStats03.png_th.png, link=[wiki:TestManagerForTracPluginGallery#Ticketstrendchart])]] 
     336 
     337'''Tickets trend chart''' [[BR]] 
     338 
     339=== Configuration === 
     340You can customize the default period of time the charts will display, in terms of historical depth and scale. 
     341 
     342To change the settings, go to the [#TestManagerSettings Test Manager Settings] administration panel, or directly edit the trac.ini file. 
     343 
     344== Importing and Exporting 
    93345 
    94346=== Importing Test Cases from a CSV file into a Test Catalog === 
    95  
    96 If you already have Test Cases defined elsewhere you can import them into the Test Manager. 
    97 While browsing a Test Catalog, click on "Import Test Cases" at the bottom of the page. The dialog box shown in the following figure will pop-up. 
    98 Browse for the CSV (comma-separated values) file containing your Test Cases, specify the value separator (default is the comma character) and click "Import". 
     347If you already have Test Cases defined elsewhere you can import them into the Test Manager. While browsing a Test Catalog, click on "Import Test Cases" at the bottom of the page. The dialog box shown in the following figure will pop-up. Browse for the CSV (comma-separated values) file containing your Test Cases, specify the value separator (default is the comma character) and click "Import". 
    99348 
    100349The CSV file must have the following format. 
     
    103352 
    104353The data must start from the second row. There must be at least the following '''required columns''': 
     354 
    105355 * title 
    106356 * description 
    107357 
    108 Any subsequent columns are optional, and will generate [wiki:TestManagerForTracPlugin#Customfields custom test case fields]. To fully appreciate custom fields, switch to the Test Catalog Tabular view. 
     358Any subsequent columns are optional, and will generate [wiki:TestManagerForTracPlugin#Customfields custom test case fields]. To fully appreciate custom fields, switch to the Test Catalog '''Tabular''' view. 
    109359 
    110360A sample CSV file may be the following: 
     361 
    111362{{{ 
    112363title,description,platform,greetings 
     
    115366Third Test Case,This is the long description for the third test case,macosx,hasta la vista 
    116367}}} 
    117  
    118 [[BR]] 
    119 [[BR]] 
    120 [[Image(screen18.png)]] 
    121 [[BR]] 
    122 '''Import Test Cases dialog''' 
    123 [[BR]] 
    124 [[BR]] 
    125  
    126 == Test Cases == 
    127 Test Cases are the smallest units of test execution. 
    128  
    129 They are implemented again as wiki pages, with a naming convention that allows the plugin code to recognize them and treat them appropriately. 
    130  
    131 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".  
    132 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. 
    133 '''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. 
    134  
    135 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. 
    136  
    137 When you are done, save the page ("Submit Changes") to save your new Test Case. 
    138  
    139 To '''delete a Test Case''' you must delete the corresponding Wiki page. 
    140  
    141 Again, notice the breadcrumbs at the top, useful to go back to the enclosing catalog or any catalog up the hierarchy. 
    142  
    143 [[BR]] 
    144 [[BR]] 
    145 [[Image(screen3.JPG)]] 
    146 [[BR]] 
    147 [[BR]] 
    148 == Moving or Copying Test Cases from one catalog to another == 
    149  
    150 It is also possible to move a single Test Case, or copy multiple Test Cases into a different catalog, with an experience similar to cut&paste. 
    151  
    152 === Moving a single Test Case === 
    153 To move a single Test Case from one catalog into a nother, you: 
    154  1. Open the Test Case 
    155  2. Click on the "Move the Test Case into another catalog" button. This is similar to a "cut" operation. 
    156  3. Navigate and open the destination catalog  
    157  4. Click on "Move the copied Test Case here" button (which only appears if a Test Case has been cut first). 
    158  
    159 It is also possible to cancel the operation at any time by clicking the "Cancel" button in a Gmail-type of yellow message at the top of the page. 
    160  
    161 [[BR]] 
    162 [[BR]] 
    163 [[Image(screen6.JPG)]] 
    164 [[BR]] 
    165 '''Moving a single Test Case''' 
    166 [[BR]] 
    167  
    168 === Copying multiple Test Cases === 
    169 To copy one or more Test Cases, even from different catalogs, and paste them all together into a destination (sub-)catalog, you: 
    170  1. Open the Catalog. Expand the tree nodes as you like. 
    171  2. Click on the "Select Multiple Test Cases" button. A checkbox appears next to every Test Case in the catalog and the sub-catalogs. See the next figure. 
    172  3. Select the Test Cases you wish to copy into another catalog. 
    173  4. Click on the "Copy the Selected Test Cases" button. This is similar to the usual "Copy" operation. 
    174  5. Navigate and open the destination catalog, or create a new one. 
    175  6. Click on "Paste the copied Test Cases here" button (which only appears if Test Cases have been copied first). 
    176  
    177 Note that the test execution statuses (i.e. successful, failed, etc...) associated to the original Test Cases in any Test Plan are not copied along with them. 
    178  
    179 [[BR]] 
    180 [[BR]] 
    181 [[Image(screen17.png)]] 
    182 [[BR]] 
    183 '''Copying multiple Test Cases''' 
    184 [[BR]] 
    185  
    186 == Test Plans == 
    187 '''Since: 1.1.0''' 
    188  
    189 A Test Plan represents a plan for a particular execution of all the Test Cases in a Test Catalog (or sub-catalog).  
    190  
    191 Think for example at the build verification test following a nightly build, or, for traditional projects, Technical Test and eventually Client Test. 
    192  
    193 Thus a Test Plan is associated to one Test Catalog, or sub-catalog. You can have any number of Test Plans for one Test Catalog, anyway. 
    194 The list of Test Plans you generated for a Test Catalog is displayd in a table at the bottom of the same catalog, as shown in the following figure. 
    195  
    196 [[BR]] 
    197 [[BR]] 
    198 [[Image(screen9.JPG)]] 
    199 [[BR]] 
    200 [[BR]] 
    201  
    202 To create a Test Plan for a catalog, open the desired Test Catalog (or sub-catalog), enter the name of the new Test Plan in the appropriate test box and click "Generate a new Test Plan". 
    203  
    204 The new Test Plan will be opened for display, showing all of the Test Cases in the catalog, in the "Untested" status. 
    205  
    206 As with Test Catalogs, you can '''choose between tree-like and a tabular representation''' of the Test Plan, as shown in the figures below. 
    207 The former is useful to actually work on the Test Plan and to view test cases before actually going and executing them. 
    208 The latter, which indicates for each Test Case the latest status modification and its author, may be useful to keep as the documentation of a just run test plan. 
    209  
    210 [[BR]] 
    211 [[BR]] 
    212 [[Image(screen7.JPG)]] 
    213 [[BR]] 
    214 '''Tree View of the Test Plan''' 
    215 [[BR]] 
    216 [[BR]] 
    217 [[Image(screen14.png)]] 
    218 [[BR]] 
    219 '''Tabular view of the Test Plan''' 
    220 [[BR]] 
    221 [[BR]] 
    222  
    223 You have two ways to set the execution status of a Test Case in a particular Test Plan: 
    224  1. Directly from the test plan tree view, by clicking on the stop-light icon and choosing the new color from the menu that opens (see next figure). (Since 1.4.7) 
    225  2. By opening the test case first, clicking on its name in the Test Plan tree, and then clicking on the corresponding stop-light at the bottom of the page, as shown in the following figure. 
    226  
    227 You don't need to save anything, the changes are immediately recorded in the database and reflected in the Test Plan. 
    228  
    229 [[BR]] 
    230 [[BR]] 
    231 [[Image(screen23.png)]] 
    232 [[BR]] 
    233 [[BR]] 
    234  
    235 [[BR]] 
    236 [[BR]] 
    237 [[Image(screen8.png)]] 
    238 [[BR]] 
    239 [[BR]] 
     368[[BR]] [[BR]][[Image(ImportTestCases01.png_th.png​, link=[wiki:TestManagerForTracPluginGallery#ImportTestCasesdialog])]] 
     369 
     370'''Import Test Cases dialog''' [[BR]] 
     371 
     372=== Exporting Test Catalogs or Test Plans into CSV file === 
     373'''Since: 1.4.9''' 
     374 
     375You can export to CSV format a Test Catalog or a Test Plan. 
     376 
     377In the Test Catalog and Test Plan pages you will find an "Export ..." button. 
     378 
     379The export format is designed for you to elaborate your external statistics, but also to eventually import the stuff back into another Test Manager plugin evironment, as soon as a compatible import feature will be implemented :D (the current import feature is simpler than that). 
     380 
     381Inside the export dialog shown in the next figure, you can specify whether the output should contain the complete text of the Test Cases, and whether this should be pre-formatted (WYSIWYG) or in raw WikiFormatting syntax. 
     382 
     383In addition to that, you can specify which column separator to use in the exported CSV file. 
     384 
     385[[BR]] [[BR]] [[Image(ExportTestCatalog01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TheExportTestCatalogdialog])]] 
     386 
     387'''The Export Test Catalog dialog'''[[BR]] 
     388 
     389== Test Artifact Change History == 
     390'''Since: 1.4.8''' 
     391 
     392On each test artifact page you will find a section named "Object change history", which contains a list of all the changes to any standard and, more interestingly, custom object's property. 
     393 
     394In the following figure you can see how the "device" custom property has been changed in a Test Plan history. 
     395 
     396[[BR]][[BR]][[Image(ObjectChangeHistory01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#ObjectchangehistoryforaTestPlan])]] 
     397 
     398'''Object change history for a Test Plan''' 
     399 
     400== Customization and Personalization == 
     401The Test Manager plugin allows for a deep customization and personalization. The elements you can customize are the following: 
     402 
     403 * Adding [#CustomFields custom fields] to the test artifacts, i.e. Test Catalogs, Test Case definitions, Test Plans, Test Case instances. It may be useful, for example, to add a "Test Effort" field to Test Cases, to be able to better plan your testing time and resources. 
     404 * [#AddingCalculatedRowstoTestCatalogsandTestPlans Adding calculated rows] to the tabular view of Test Catalogs and Test Plans. Available operations are Sum, Average and Count of the values in any column, including custom fields. For example, if you added a "Test Effort" custom field to your Test Cases, you may want the total Test Effort calculated for each catalog and displayed at the bottom of it. 
     405 * Defining [#CustomTestCaseOutcomesi.e.statesverdicts Custom Test Case Outcomes (i.e. states, verdicts)] to fit your quality process. 
     406 * Adding a [#CustomizableWorkflow Workflow] to any of your test artifacts. For example, you may want to have an approval workflow for new test case definitions, or be able to assign test plans or individual cases to specific test engineers to be run, and manage their completion status. 
     407 * Adding [#TestArtifactTemplates Test Artifact Templates] for Test Catalogs and Test Cases, and specifying which default template should be used for new test cases in any particular catalog. 
     408 
     409In addition to these, you can personalize several aspects of the Test Manager behavior, by means of the [#TestManagerSettings Test Manager Settings] administration panel. 
     410 
     411=== Custom fields === 
     412'''Since: 1.2.0''' 
     413 
     414Custom fields can be added to the four test objects and to the [wiki:TestManagerForTracPluginWorkflow workflow] state object, by declaring them in the trac.ini file. 
     415 
     416The syntax is the same used for custom Ticket properties, only the name of the ini file sections are specific: you must use the test artifact type name followed by "-tm_custom". 
     417 
     418The test artifacts type names are the following: 
     419 
     420 * testcatalog 
     421 * testcase 
     422 * testplan 
     423 * testcaseinplan 
     424 
     425For example, the following sections in the trac.ini file define custom properties for each of the above artifacts. 
     426 
     427{{{ 
     428[testcatalog-tm_custom] 
     429remarks = text 
     430remarks.label = Remarks 
     431 
     432[testcase-tm_custom] 
     433component = select 
     434component.label = Component 
     435component.options = Framework|Backend|GUI 
     436component.value = GUI 
     437 
     438testeffort = text 
     439testeffort.label = Test Effort 
     440testeffort.value = 0 
     441 
     442required = checkbox 
     443required.label = Required 
     444required.value = 0 
     445 
     446[testplan-tm_custom] 
     447longdescription = textarea 
     448longdescription.label = Test Plan Description 
     449longdescription.rows = 10 
     450longdescription.cols = 50 
     451 
     452[testcaseinplan-tm_custom] 
     453operating_system = radio 
     454operating_system.label = Operating System 
     455operating_system.options = Windows|Linux|Macosx|Android|iOS|Other 
     456operating_system.value = Linux 
     457}}} 
     458Once defined in the trac.ini file as above, custom fields will be available to the User for browse and for editing in the Web page, as shown next. 
     459 
     460'''Note: Editing custom properties requires the TEST_MODIFY permission.''' 
     461 
     462The following screenshot shows a custom "platform" field added to the Test Case artifact, and how it is presented to the User for editing. 
     463 
     464The value is initially displayed read-only, as a label. Clicking on the pencil icon turns the label into an text field, allowing the User to edit the value, and also displays a '''Save''' button. Clicking the button immediately saves the new value into the database. 
     465 
     466[[BR]] [[BR]] [[Image(CustomFields01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#EditingacustomOperatingSystempropertyonaTestcaseinaPlan])]] 
     467 
     468'''Editing a custom "Operating System" property on a Test case in a Plan''' 
    240469 
    241470=== Custom Test Case Outcomes (i.e. states, verdicts) === 
     
    253482default = to_be_tested 
    254483}}} 
    255  
    256 You can '''customize the outcomes''' at any moment by adding new outcomes, or modify the descriptions of the current ones.  
    257 Do not delete previous outcomes if you have already assigned them to any of your test cases. 
     484You can '''customize the outcomes''' at any moment by adding new outcomes, or modify the descriptions of the current ones. Do not delete previous outcomes if you have already assigned them to any of your test cases. 
    258485 
    259486For example, to add a new outcome named "It's a Mess!!!" to the failures, add a line like the following, in trac.ini: 
     
    262489red.bigmess = It's a Mess!!! 
    263490}}} 
    264  
    265 You will now be able to choose it when assigning a test case status using the semaphore, which now shows a more complete menu to choose from. 
    266 See the following figure. 
    267  
    268 [[BR]] 
    269 [[BR]] 
    270 [[Image(screen15.png)]] 
    271 [[BR]] 
    272 [[BR]] 
    273  
    274 === Linking a Ticket to a Test Case === 
    275 When viewing a Test Case, you can open a new Ticket by means of the "Open Ticket on this Test Case" button.  
    276  
    277 The new ticket will contain a link back to the corresponding Test Case and, if you were viewing it in the context of a particular Test Plan, of the Test Plan as well. 
    278 Additionally, a '''[wiki:TestManagerForTracPluginApi#GettingalltheTicketsrelatedtoaTestCase programmatic Python API]''' is provided to retrieve all of the Tickets opened against a Test Case, in all or in a specific Test Plan. 
    279  
    280 This plugin also supports the TracTicketTemplatePlugin to fill a ticket template with this information. In this case, you can use the following parameters in the template to receive the information: 
    281  
    282  * testCaseNumber: The wiki page for the corresponding Test Case 
    283  * planId: The ID of the Test Plan 
    284  * planName: The name of the Test Plan 
    285  
    286 For example, to get the test case number, you template will have something like: 
    287 {{{ 
    288   bleah bleah 
    289   Test Case: %(testCaseNumber)s 
    290   bleah bleah 
    291 }}} 
    292  
    293 === Showing Tickets related to a Test Case === 
    294  
    295 While browsing a Test Case, either inside or outside of a Test Plan, you can show all of its related Tickets - i.e. Tickets that were opened using the above "Open a Ticket on this Test Case" button. 
    296  
    297 To do this, just browse the Test Case and '''click on the "Show Related Tickets" button'''. 
    298  
    299 If you are browsing a Test Case "definition", i.e. from a Test Catalog, you will be shown all of the Tickets opened against the Test Case '''in any Test Plan'''. 
    300  
    301 If you are instead browsing a Test Case in a specific Test Plan, you will be shown all of the Tickets opened against the Test Case '''in that specific Test Plan'''. 
    302  
    303 See the following figure for what happens when you click on the "Show Related Tickets" button from the Test Case shown at the previous section. 
    304  
    305 [[BR]] 
    306 [[BR]] 
    307 [[Image(screen16.png)]] 
    308 [[BR]] 
    309 [[BR]] 
    310  
    311 == Exporting Test Catalogs or Test Plans into CSV file == 
    312 '''Since: 1.4.9''' 
    313  
    314 You can export to CSV format a Test Catalog or a Test Plan. 
    315 [[BR]] 
    316 In the Test Catalog and Test Plan pages you will find an "Export ..." button. 
    317 [[BR]] 
    318 The export format is designed for you to elaborate your external statistics, but also to eventually import the stuff back into another Test Manager plugin evironment, as soon as a compatible import feature will be implemented :D (the current import feature is simpler than that). 
    319 [[BR]] 
    320 In the export dialog dhown in the next figure, you can specify whether the output should contain the complete text of the Test Cases, and whether this should be pre-formatted (WYSIWYG) or in raw WikiFormatting syntax. 
    321  
    322 In addition to that, you can specify which column separator to use in the exported CSV file. 
    323  
    324 [[BR]] 
    325 [[BR]] 
    326 [[Image(screen25.png)]] 
    327 [[BR]] 
    328 [[BR]] 
    329  
    330 == Custom fields == 
     491You will now be able to choose it when assigning a test case status using the traffic light, which now shows a more complete menu to choose from. See the following figure. 
     492 
     493[[BR]][[BR]][[Image(CustomOutcomes01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#SettingacustomoutcometoaTestCaseinaPlan])]] 
     494 
     495'''Setting a custom outcome to a Test Case in a Plan''' 
     496 
     497=== Customizable Workflow === 
    331498'''Since: 1.2.0''' 
    332499 
    333 Custom fields can be added to the four test objects and to the [wiki:TestManagerForTracPluginWorkflow workflow] state object, by declaring them in the trac.ini file. 
    334  
    335 The syntax is the same used for custom Ticket properties, only the name of the ini file sections are specific: you must use the test artifact type name followed by "-tm_custom". 
    336  
    337 The test artifacts type names are the following: 
    338  * testcatalog 
    339  * testcase 
    340  * testplan 
    341  * testcaseinplan 
    342  
    343 For example, the following sections in the trac.ini file define one custom property for each of the above artifacts. 
    344  
    345 {{{ 
    346     [testcatalog-tm_custom] 
    347     prop1 = text 
    348     prop1.value = Default value 
    349     prop1.label = Property One 
    350  
    351     [testcaseinplan-tm_custom] 
    352     os = text 
    353     os.value = windows 
    354     os.label = Operating System 
    355  
    356     [testcase-tm_custom] 
    357     nice_prop = text 
    358     nice_prop.value = My friend 
    359  
    360     [testplan-tm_custom] 
    361     good_prop = text 
    362     good_prop.value = linux 
    363 }}} 
    364  
    365 '''Note: Only text property types are currently supported.''' 
    366  
    367 Once defined in the trac.ini file as above, custom fields will be available to the User for browse and for editing in the Web page, as shown next. 
    368  
    369 '''Note: Editing custom properties requires the TEST_MODIFY permission.''' 
    370  
    371 The following screenshot shows a custom "platform" field added to the Test Case artifact, and how it is presented to the User for editing. 
    372  
    373 The value is initially displayed read-only, as a label. Clicking on the pencil icon turns the label into an edit box, allowing the User to edit the value and also displays a "Save" button. Clicking the button immediately saves the new value into the database. 
    374  
    375 [[BR]] 
    376 [[BR]] 
    377 [[Image(screen11.png)]] 
    378 [[BR]] 
    379 [[BR]] 
    380 [[BR]] 
    381  
    382 == Customizable Workflow == 
    383 '''Since: 1.2.0''' 
    384  
    385 The following figure shows a sample [wiki:TestManagerForTracPluginWorkflow workflow] added to Test Cases with custom sample operations. 
    386 No built-in operation is currently implemented but the sample one shown here, named 'sample_operation', which logs a debug message with the text input by the User. 
     500The following figure shows a sample [wiki:TestManagerForTracPluginWorkflow workflow] added to Test Cases with custom sample operations. No built-in operation is currently implemented except for the sample one shown here, named 'sample_operation', which logs a debug message with the text input by the User. 
    387501 
    388502Every object which has a workflow defined is created in a "new" state, so every transition should consider this as the first state in the state machine. 
    389503 
    390 This is a sample content of the trac.ini file to associate a workflow to the Test Case object. 
    391 [[BR]] 
     504This is a sample content of the trac.ini file to associate a workflow to the Test Case object. [[BR]] 
    392505 
    393506{{{ 
    394507[testcase-resource_workflow] 
    395 sleep = new -> asleep 
    396 sleep.permissions = TEST_MODIFY 
    397  
    398 sing = new -> singing 
    399 sing.permissions = TEST_MODIFY 
    400 sing.operations = sample_operation 
    401  
    402 calmdown = singing -> calm 
    403 calmdown.permissions = TEST_MODIFY 
    404  
    405 kill = asleep,calm -> dead 
    406 kill.permissions = TEST_MODIFY 
    407 }}} 
    408  
    409 [[BR]] 
    410 Refer to the [wiki:TestManagerForTracPluginWorkflow Workflow Engine] description page for more details. 
    411  
    412 [[BR]] 
    413 [[BR]] 
    414 [[Image(screen12.png)]] 
    415 [[BR]] 
    416 [[BR]] 
    417 [[BR]] 
    418  
    419 == Searching and filtering Test Cases in the tree view == 
    420 A type-ahead, browser-side filtering feature allows for easily locating Test Cases matching a particular naming convention in the title, and/or a particular execution status. 
    421  
    422 This is available both in the context of a Test Catalog and in Test Plans. 
    423  
    424 Multiple words (or parts of) separated by blanks are supported, in AND condition. 
    425  
    426 In the case of a Test Plan, you can also add a test case status to filter by this criterion.  
    427 The supported statuses are (even substrings of): 
    428  * untested 
    429  * successful 
    430  * failed 
    431  
    432 [[BR]] 
    433 [[BR]] 
    434 [[Image(screen4.JPG)]] 
    435 [[BR]] 
    436 [[BR]] 
    437 [[BR]] 
    438  
    439 == Test Artifact Change History == 
    440 '''Since: 1.4.8''' 
    441  
    442 On each test artifact page you will find a section named "Object change history", which contains a list of all the changes to any standard and, more interestingly, custom object's property. 
    443  
    444 In the following figure you can see how the "device" custom property has been changed in a Test Plan history. 
    445  
    446 [[BR]] 
    447 [[BR]] 
    448 [[Image(screen24.png)]] 
    449 [[BR]] 
    450 '''Object change history for a Test Plan''' 
    451  
    452 == Test Management and Execution Statistics == 
    453 '''Since: 1.1.1''' 
    454  
    455 Charting capabilities allow for tracking the evolution of the test suites, the corresponding test plans and tickets opened against test cases. 
    456  
    457 To access the test management statistics, click on '''Test Stats''' in the Trac toolbar on the upper right corner of the page. 
    458  
    459 As shown in the next figure, a chart will be displayed with statistics about all the test cases in the system and a default period of time, with more charts available in the other tabs. 
    460  
    461 There are three charts available: 
    462  
    463 === Test activity trend chart === 
    464  
    465 Displays the number of test cases created during time and the trend of the test activity, in terms of test cases to be tested, successful and failed. 
    466  
    467 By means of the filtering criteria at the bottom of the chart, you can select the desired period of time, the chart resolution (in terms of time between different samples) and the Test Plan for your chart. 
    468  
    469 You can bookmark the URL named "Static URL" at the bottom of the page in order to go directly with the current selected filtering criteria. 
    470  
    471 [[BR]] 
    472 [[BR]] 
    473 [[Image(screen20.png)]] 
    474 [[BR]] 
    475 '''Test activity trend chart''' 
    476 [[BR]] 
    477  
    478 === Current test status chart === 
    479  
    480 Shows the current status of the test activity for all test plans of a specific plan, displaying the number of tests that are successful, failed and yet to be tested. 
    481  
    482 [[BR]] 
    483 [[BR]] 
    484 [[Image(screen21.png)]] 
    485 [[BR]] 
    486 '''Current test status chart''' 
    487 [[BR]] 
    488  
    489 === Tickets trend chart === 
    490  
    491 As long as [wiki:TestManagerForTracPlugin#LinkingaTickettoaTestCase tickets have been opened from the context of a test case in a plan], by means of the appropriate "Open a ticket on this test case" button, this chart shows the trend in tickets associated with all test plans or a specific plan, displaying the number of total, active (i.e. not closed) and closed tickets. 
    492  
    493 [[BR]] 
    494 [[BR]] 
    495 [[Image(screen22.png)]] 
    496 [[BR]] 
    497 '''Tickets trend chart''' 
    498 [[BR]] 
    499  
    500 === Configuration === 
    501  
    502 '''Note:''' By default, the charts use the [http://developer.yahoo.com/yui/charts YUI library] available online at Yahoo!, so you will need internet connection from your client machines to be able to display this charts.  
    503  
    504 Alternatively, in case you don't have internet connection, you can download the YUI library, put it somewhere on the Trac server machine where the web server can access it, and refer its location in the trac.ini as follows.  
    505  
    506 Other options you can customize are the default period of time the charts will display, in terms of historical depth and scale. 
     508review = new,changes_requested -> under_review 
     509review.permissions = TEST_MODIFY 
     510 
     511reject = under_review -> rejected 
     512reject.permissions = TEST_MODIFY 
     513reject.operations = sample_operation 
     514 
     515request_changes = under_review -> changes_requested 
     516request_changes.permissions = TEST_MODIFY 
     517request_changes.operations = sample_operation 
     518 
     519accept = under_review -> accepted 
     520accept.permissions = TEST_MODIFY 
     521}}} 
     522[[BR]] Refer to the [wiki:TestManagerForTracPluginWorkflow Workflow Engine] description page for more details. 
     523 
     524[[BR]] [[BR]] [[Image(Workflow01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#AcustomworkflowappliedtoTestCasesinaPlan])]] 
     525 
     526'''A custom workflow applied to Test Cases in a Plan'''[[BR]] [[BR]] 
     527 
     528=== Test Artifact Templates === 
     529Your quality process may require your test catalogs and test cases to follow particular templates. With the Test Manager, you can define templates for your test catalogs and your test cases. When you create a new test catalog or test case, their description will be filled with the templates you have defined. 
     530 
     531To create templates, open the '''Administration''' tab and go to the '''Test Manager -> Templates '''section. 
     532 
     533[[Image(Templates01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TheTemplatesmanagementsectionintheTestManagerAdministrationpanel])]] 
     534 
     535'''The Templates management section in the Test Manager Administration panel''' 
     536 
     537==== Test Catalog Templates ==== 
     538In this section you can manage the templates for your Test Catalogs. 
     539 
     540If you have any templates defined, they will be listed in this section. Otherwise, the text "No templates created yet" will be displayed. 
     541 
     542 * To '''create''' a new template, type the new template name in the text field and click '''Add Test Catalog Template'''. The template editing page will be opened. 
     543   * Enter the main text for the Test Catalog template in the text area. 
     544   * To preview the results, push '''Preview Template''': the preview will be displayed right below the text area. 
     545   * When you are satisfied with the template, push '''Submit Changes'''. 
     546   * Push Cancel to exit without saving. 
     547 * To '''browse or modify''' a template, click on the template name. The template editing page will be opened in edit mode. 
     548   * Follow the same options as for creating a new template. 
     549 * To '''delete''' one or more templates, select the corresponding checkboxes and push '''Delete Selected'''. 
     550 
     551==== Test Case Templates ==== 
     552In this section you can manage the templates for your Test Cases. 
     553 
     554If you have any templates defined, they will be listed in this section. Otherwise, the text "No templates created yet" will be displayed. 
     555 
     556 * To '''create''' a new template, type the new template name in the text field and click '''Add Test Catalog Template'''. The template editing page will be opened. 
     557   * Enter the main text for the Test Case template in the text area. 
     558   * To preview the results, push '''Preview Template''': the preview will be displayed right below the text area. 
     559   * When you are satisfied with the template, push '''Submit Changes'''. 
     560   * Push Cancel to exit without saving. 
     561 * To '''browse or modify''' a template, click on the template name. The template editing page will be opened in edit mode. 
     562   * Follow the same options as for creating a new template. 
     563 * To '''delete''' one or more templates, select the corresponding checkboxes and push '''Delete Selected'''. 
     564 
     565==== Default template for Test Catalog ==== 
     566Here you can set the default template for new Test Catalogs. 
     567 
     568Select the desired template from the list, or select None to not have any template applied, and click '''Save Default Test Catalog Template'''. 
     569 
     570==== Default Test Case template for each Test Catalog ==== 
     571Here you can specify, for each Test Catalog you have already defined, which should be the default template for the Test Cases defined therein. 
     572 
     573Select the desired Test Case template from the list associated to any particular Test Catalog, or select None to not have any template applied, and click '''Save Template Configuration'''. 
     574 
     575=== Test Manager Settings === 
     576Several aspects of the Test Manager operations are for you to personalize. To do this, you can either use the '''Test Manager''' administration panel, or directly edit the trac.ini file. 
     577 
     578The following paragraphs outline the administration panel sections. 
     579 
     580When you are done with your changes, click '''Save''' at the bottom of the page. 
     581 
     582[[Image(Settings01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TheSettingssectionintheTestManagerAdministrationpanel])]] 
     583 
     584'''The Settings section in the Test Manager Administration panel''' 
     585 
     586==== Test Statistics default settings ==== 
     587You can personalize the default period of time the statistical charts will display, in terms of historical depth and scale. 
     588 
     589 * Number of days shown by default: determines the historical depth of the charts, in terms of days back from the current date. 
     590 * Number of days between each data point: determines the scale, or granularity, of the charts, in terms of days per single piece of data. 
     591 
     592In alternative to using the administraiton panel, you can directly edit the trac.ini file: 
    507593 
    508594{{{ 
    509595[testmanager] 
    510 yui_base_url = <URL or path to the root of your YUI library> 
    511596default_days_back = <number of days back from today> 
    512597default_interval = <number of days between samples> 
    513598}}} 
    514  
    515599For example: 
    516600 
    517601{{{ 
    518602[testmanager] 
    519 yui_base_url = http://yui.yahooapis.com/2.9.0 
    520603default_days_back = 14 
    521604default_interval = 1 
    522605}}} 
     606==== Test Manager visualization settings ==== 
     607You can personalize some visualization settings: 
     608 
     609 * Sort a test plan's test cases by: Determines how the test cases in a Test Plan will be sorted. 
     610   * User Specified: You can control the exact ordering of the test cases. To set a specific order, use the [# Organize Test Catalogs] functionality. 
     611   * Name: Sorts the test cases by title. 
     612   * Modification Time: Sorts the test cases by modification time, with the most recent on top. 
     613 * Open Test Cases in a new window: Determines whether, from a test catalog or test  plan view, clicking on a test case will display it in a new window or in the same window. 
     614 * Default Test Catalog view type: Determines whether the default view for test catalogs should be Tree or Table. 
     615 * Default Test Plan view type: Determines whether the default view for test plans should be Tree or Table. 
     616 
     617==== Visible Test Catalog columns in table view ==== 
     618You can personalize the visible columns for the Trest Catalog and for the Test Plan tabular views. 
     619 
     620The two lists show the avilable columns, including [#Customfields custom fields], for the two artifact types. Use the checkbox to display or hide the corresponding column in the table. 
     621 
     622For each column, you can choose to add a calculated "totals" row at the end of the table, showing for all the test cases: 
     623 
     624 * Sum: the sum of the non-empty values in the column. 
     625 * Average: the average of the non-empty values in the column. 
     626 * Count: the count of the non-empty values in the column. 
     627 
     628This can be found particularly useful if you set up [#Customfields custom fields]. Refer to the corresponding section for details and usage examples. 
    523629 
    524630== Security == 
    525  
    526631The following new permissions are available to manage the Test Manager security: 
    527632 
     
    531636 * TEST_DELETE - Ability to delete test cases 
    532637 * TEST_PLAN_ADMIN - Ability to generate and delete test plans 
    533  * TEST_STATS_VIEW - Ability to view test management statistics  
    534  
    535 [[BR]][[BR]] 
     638 * TEST_STATS_VIEW - Ability to view test management statistics 
     639 
    536640== Programmatic API == 
    537  
    538641The '''programmatic RESTful API''' is documented in details in this page TestManagerForTracPluginApi. 
    539642 
    540  
    541 [[BR]][[BR]] 
    542 == Tutorial (as powerpoint presentation) == 
    543 '''TODO:''' These tutorials document release 1.0.3 and so need to be updated with the Test Plan and other recent features. 
     643== Tutorial == 
     644'''TODO:''' These tutorials document release 1.0.3 and so need to be updated with the Test Plan and other recent features. Refer to the '''[http://www.youtube.com/watch?v=BIi3QMT0rT4 Video tutorial on Youtube]''' for more up-to-date information. 
    544645 
    545646 * attachment:"UserGuide_part_1.ppt" 
     
    547648 * attachment:"UserGuide_part_3.ppt" 
    548649 
    549 [[BR]][[BR]] 
    550650== Project site == 
    551651Project site: http://sourceforge.net/projects/testman4trac/ 
     
    553653The project is also on Pypi: http://pypi.python.org/pypi/TestManager 
    554654 
    555 [[BR]][[BR]] 
    556655== Translations == 
    557  
    558656This plugin is localized and all texts and messages will be displayed in the language detected by the User's browser, if available, or in English otherwise. 
    559657 
     
    564662[https://sourceforge.net/projects/testman4trac/forums/forum/1200600 Contact me on the forum] and I'll manage to add it to the set of available languages. 
    565663 
    566 Top translations » [https://www.transifex.net/projects/p/testman4trac/ Test Manager for Trac Plugin on Transifex] 
    567 [[BR]] 
    568 [[Image(http://www.transifex.net/projects/p/testman4trac/chart/image_png, title=Test Manager for Trac Plugin project page on Transifex.net, link=http://www.transifex.net/projects/p/testman4trac)]] 
    569 [[BR]] 
    570 Kindly provided by [[Image(https://ds0k0en9abmn1.cloudfront.net/static/charts/images/tx-logo-micro.png, link=http://www.transifex.net/, title=the open translation platform, valign=bottom)]] 
    571  
    572 [[BR]][[BR]] 
    573 == Bugs/Feature Requests ==  
    574  
    575 If you have any issues, create a  
    576 [http://trac-hacks.org/newticket?component=TestManagerForTracPlugin&owner=seccanj new ticket]. 
    577  
    578 Existing bugs and feature requests for TestManagerForTracPlugin are  
    579 [report:9?COMPONENT=TestManagerForTracPlugin here]. 
    580  
    581 [[TicketQuery(component=TestManagerForTracPlugin,format=table,col=summary|status|severity|type|owner|time)]] 
    582  
    583 [[BR]][[BR]] 
     664Top translations » [https://www.transifex.net/projects/p/testman4trac/ Test Manager for Trac Plugin on Transifex] [[BR]] [[Image(http://www.transifex.net/projects/p/testman4trac/chart/image_png, title=Test Manager for Trac Plugin project page on Transifex.net, link=http://www.transifex.net/projects/p/testman4trac)]] [[BR]] Kindly provided by [[Image(https://ds0k0en9abmn1.cloudfront.net/static/charts/images/tx-logo-micro.png, link=http://www.transifex.net/, title=the open translation platform, valign=bottom)]] 
     665 
     666== !Bugs/Feature Requests == 
     667 
     668In '''[TestManagerForTracPluginBugsFeatures this page]''' you can browse the existing bugs and feature requests for TestManagerForTracPlugin of open a new one. 
     669 
    584670== Download == 
    585  
    586671Download the egg files, ready to be installed, from the project site [http://sourceforge.net/projects/testman4trac/files here]. 
    587672 
    588 [[BR]][[BR]] 
    589673== Source == 
    590  
    591674You can download the source code from [https://sourceforge.net/projects/testman4trac/files here]. 
    592675 
    593 [[BR]][[BR]] 
    594676== Installation == 
    595  
    596677'''Trac 0.11, 0.12 and 1.x are supported''', and also '''Python 2.5, 2.6 and 2.7'''. 
    597678 
     
    606687The functionalities are divided in three plugins, which must be installed in this order: 
    607688 
    608     1) Trac Generic Class 
    609  
    610     2) Trac Generic Workflow 
    611  
    612     3) Test Manager 
    613  
     689  1) Trac Generic Class 
     690 
     691  2) Trac Generic Workflow 
     692 
     693  3) Test Manager 
    614694 
    615695An additional plugin is only useful for debugging and should not be installed in a production environment. 
    616696 
    617     * SQL Executor 
    618  
    619 With the latter plugin, you can perform arbitrary SQL queries on the Trac database from a web browser.  
    620 Just type on the URL: 
    621   !http://yourserver/yourenvironment/sqlexec?sql=any SQL statement 
     697 * SQL Executor 
     698 
     699With the latter plugin, you can perform arbitrary SQL queries on the Trac database from a web browser.  Just type on the URL: 
     700 
     701  !http://yourserver/yourenvironment/sqlexec?sql=any                         SQL statement 
    622702 
    623703For example: 
    624   !http://localhost/sampleproject/sqlexec?sql=select * from testcatalog 
    625  
    626  
    627 Follow the tutorial presentation that you can download from the project site to start.  
    628 The tutorial is actually very old and needs to be updated to the new Test Plans and other features, but it will get you started. 
    629  
    630 [[BR]][[BR]] 
     704 
     705  !http://localhost/sampleproject/sqlexec?sql=select                         * from testcatalog 
     706 
     707Follow the tutorial presentation that you can download from the project site to start.  The tutorial is actually very old and needs to be updated to the new Test Plans and other features, but it will get you started. 
     708 
    631709== Troubleshooting == 
    632  
    633 === Is setuptools properly installed? === 
     710'''Is setuptools properly installed?''' 
    634711 
    635712Try this from the command line: 
     
    638715$ python -c "import pkg_resources" 
    639716}}} 
    640  
    641717If you get no output, setuptools is installed. Otherwise, you'll need to install it before plugins will work in Trac. 
    642718 
    643 === Did you get the correct version of the Python egg? === 
    644  
    645 Python eggs have the Python version encoded in their filename. For example, MyPlugin-1.0-py2.4.egg is an egg for Python 2.5, and will not be loaded if you're running a different Python version (such as 2.6 or 2.7). 
     719'''Did you get the correct version of the Python egg?''' 
     720 
     721Python eggs have the Python version encoded in their filename. For example, `TestManager-1.0.0-py2.7.egg` is an egg for Python 2.7, and will not be loaded if you're running a different Python version (such as 2.5 or 2.6). 
    646722 
    647723Also, verify that the egg file you downloaded is indeed a ZIP archive and not the HTML preview page instead. 
    648724 
    649 === Is the plugin enabled? === 
     725'''Is the plugin enabled?''' 
    650726 
    651727If you install a plugin globally (i.e. not inside the plugins directory of the Trac project environment) you will have to explicitly enable it in trac.ini. Make sure that: 
     
    661737 * the value is "enabled", not e.g. "enable" 
    662738 
    663 === Check the permissions on the egg file and on the trac.ini file === 
    664  
    665 The user user to run Trac (either tracd or Apache) must be able to read the egg files.  
     739'''Check the permissions on the egg file and on the trac.ini file''' 
     740 
     741The user user to run Trac (either tracd or Apache) must be able to read the egg files. 
    666742 
    667743Also, it's been reported that for PosgreSQL also its user must be able to read trac.ini. 
    668744 
    669 === Check the log files === 
     745'''Check the log files''' 
    670746 
    671747Open the Trac Admin tab, enable logging and set the log level to DEBUG, then watch the log file for messages about loading plugins. 
    672748 
    673 === Verify you have proper permissions === 
    674  
    675 Some plugins, including the Test Manager ones, require you have special permissions in order to use them.  
    676  
    677 See [wiki:TestManagerForTracPlugin#Security] for a description of the available/required permissions. 
    678  
    679 === Is the wrong version of the plugin loading? === 
     749'''Verify you have proper permissions''' 
     750 
     751Some plugins, including the Test Manager ones, require you have special permissions in order to use them. 
     752 
     753See TestManagerForTracPlugin#Security for a description of the available/required permissions. 
     754 
     755'''Is the wrong version of the plugin loading?''' 
    680756 
    681757If you put your plugins inside plugins directories, and certainly if you have more than one project, you need to make sure that the correct version of the plugin is loading. Here are some basic rules: 
     
    689765Having more than one version listed inside Python site-packages is fine (ie. installed with setup.py install) - setuptools will make sure you get the version installed most recently. However, '''don't store more than one version inside a global or project plugins directory''' - neither version number nor installed date will matter at all. There is no way to determine which one will be located first when Trac searches the directory for plugins. 
    690766 
    691 === Have you restarted Apache? === 
     767'''Have you restarted Apache?''' 
    692768 
    693769For Apache to sense a plugin upgrade (and sometimes even installation), it must be restarted. 
    694770 
    695 === If all of the above failed === 
    696  
    697 OK, so the logs don't mention plugins, the egg is readable, the python version is correct and the egg has been installed globally (and is enabled in the trac.ini), you restarted Apache and it still doesn't work or give any error messages or any other indication as to why?  
     771'''If all of the above failed''' 
     772 
     773OK, so the logs don't mention these plugins, the egg is readable, the python version is correct and the egg has been installed globally (and is enabled in the trac.ini), you restarted Apache and it still doesn't work or give any error messages or any other indication as to why? 
    698774 
    699775Open a ticket here. The plugins maintainers (yes, it's me :-)) watch ticket notifications continuously. 
    700776 
    701 [[BR]][[BR]] 
    702777== Recent Changes == 
    703778Note: you can '''subscribe to the [https://sourceforge.net/projects/testman4trac/forums/forum/1200598 Forum]''' to be updated on new releases. 
    704 [[BR]] 
    705 [[BR]] 
    706 '''During the last months:''' 
    707 [[BR]] 
    708 [[BR]] 
    709  
    710 '''Release 1.7.3 (2013-12-01):''' 
    711  
    712   A brand new Russian translation is available: thanks Valeriy Gusev! 
    713    
    714   o Enhancement #11381 (Trac-Hacks): Ability to add test case in more than one test plan 
    715  
    716 '''Release 1.7.2 (2013-11-01):''' 
    717  
    718   A brand new Korean translation is available: thanks Mandy Cho! 
    719    
    720   The French translation has also been greatly updated: thanks Laura!!! 
    721  
    722   o Fixed Ticket #11358 (Track-Hacks): Adding custom [test-outcomes] breaks setting outcomes from Test Plan table view 
    723    
    724   o Fixed Ticket #11347 (Track-Hacks): Show related tickets issue  
    725  
    726   o Fixed Ticket #11350 (Track-Hacks): Add to Test Plan Button doesn't work  
    727  
    728 '''Release 1.7.1 (2013-08-16):''' 
    729  
    730   o To facilitate packaging for Debian, the test statistics were completely rewritten against the Flot library, removing 
    731     the dependency on the YUI library, which was based on Flash. 
    732          
    733   o Added some small usability improvements, like the folder icons for test catalogs. 
    734    
    735   o Fixed Ticket #11123 (Track-Hacks): Test Stats fail to update charts 
    736    
    737   o Fixed Ticket #11142 (Track-Hacks): Test Cases or Test Catalogs fails with exception  
    738     "AttributeError: 'NoneType' object has no attribute 'split'" 
    739  
    740 '''Release 1.6.2 (2013-05-23):''' 
    741  
    742   o Enhanced the look&feel of the new "Organize Test Catalogs" dialog box. 
    743  
    744   o Fixed Ticket #11055 (Track-Hacks): UnicodeEncodeError when using testcase-name with non-ascii-characters 
    745  
    746   o Fixed Ticket #11113 (Track-Hacks): Links to JQuery and JQuery-UI JS not updated for new versions - Stats don't show 
    747  
    748 '''Release 1.6.1 (2013-04-21):''' 
    749  
    750   o Enhancement #10672 (Trac-Hacks): Status summary for the directory in the testplans. 
    751                                      In the test plan view, now a semaphore is displayed next to each 
    752                                      test catalog node, with the aggregated (worst) status of all the sub-tree.   
    753  
    754   o Enhancement #10907 (Trac-Hacks): Custom execution order for test cases. 
    755                                      Test cases can now be organized in catalogs with the order of your choice. 
    756                                      You can also easily drag and drop test cases from one catalog to another. 
    757  
    758   o Enhancement #10807 (Trac-Hacks): Cloning a test plan 
    759  
    760   o Fixed Ticket #10568 (Track-Hacks): Can't edit test case templates 
    761  
    762   o Fixed Ticket #10295 (Track-Hacks): Trac detected an internal error: !UnicodeError: source returned bytes, but no encoding specified[[BR]] 
    763  
    764 '''Release 1.5.2 (2012-10-14):''' 
    765  
    766   This release makes the plugins compatible with Trac 1.0. 
    767    
    768   Since the release of Trac 1.0, I had to split the plugins code into  
    769   two versions: 
    770     o A version that works well with Trac 0.11 
    771     o A version that works well with Trac 0.12 and Trac 1.0 
    772           
    773   All the code still works with Python 2.5, 2.6 and 2.7. 
    774   All database backends are still supported. 
    775  
    776   To build from the source, refer to the updated BUILD.txt file.   
    777  
    778   o Fixed Ticket #10293 (Track-Hacks): New install impossible on Trac 1.0beta1 
    779    
    780   o Fixed Ticket #10295 (Track-Hacks): Trac detected an internal error: !UnicodeError: source returned bytes, but no encoding specified[[BR]] 
    781    
    782 '''Release 1.5.1 (2012-08-12):''' 
    783  
    784   This is somewhat of a major release, in that it includes several new interesting features and many bug fixes. 
    785   See the list below for more details.[[BR]] 
    786    
    787   In addition to that, I realized a VIDEO TUTORIAL showing out the main features of this Test Manager, to  
    788   help new and existing users take confidence with recent changes, new features and so on.[[BR]] 
    789    
    790   Check the tutorial on YouTube: [http://www.youtube.com/watch?v=BIi3QMT0rT4] [[BR]] 
    791    
    792   Also the trac-hacks user manual has been restructured, updated and enriched with the recent changes and features. 
    793  
    794   o Enhancement #353771 (!SourceForge): Time tracking capability. [[BR]] 
    795                                         
    796                                        This is now possible by means of the enhancements to the tabular views of 
    797                                        both test catalogs and test plans and the addition of a custom field. 
    798                                        See the comments to the feature request and the video tutorial, where this 
    799                                        customization example is fully explored. [[BR]] 
    800  
    801   o Enhancement #3537704 (!SourceForge): Possibility to select columns for the table view. [[BR]] 
    802                                          
    803                                         This is now possible from the administration panel. [[BR]] 
    804                                          
    805                                         I also added an interesting feature that allows for adding a statistical 
    806                                         row to the test catalog and test plan tabular views, with the option to  
    807                                         have the sum, average or count of the values in any column, being it a  
    808                                         standard or a custom property of test cases or catalogs. [[BR]] 
    809                                          
    810                                         This feature is also used to realize the feature #353771 above. 
    811                                         See the video tutorial for an interesting use of this one to track test 
    812                                         execution effort estimation of an entire test plan  and compare it to   
    813                                         actual execution time. [[BR]] 
    814                                         
    815   o Enhancement #3537700 (!SourceForge): Option to select table view as default view.  
    816                                         This is now possible from the administration panel. [[BR]] 
    817                                     
    818   o Enhancement #3537696 (!SourceForge): Possibility to change test plans. [[BR]] 
    819                                          
    820                                         This is now possible by means of several new actions available on test  
    821                                         cases: 
    822                                          - On a test case definition page, you have a new action button to add the  
    823                                            test case to a plan. A dialog box appears showing you the suitable plans  
    824                                            (the ones not containing all test cases). 
    825                                          - On a test case instance (a test case inside a plan) page, you have a new  
    826                                            action button to remove the test case from the plan. 
    827                                          - On a test case instance (a test case inside a plan) page, in case the plan 
    828                                            is containing an old snapshot of the test case and you wish to update  
    829                                            its text description to the latest version, you have a new action button  
    830                                            to do that. [[BR]] 
    831                                         
    832   o Fixed Ticket #8932 (Track-Hacks): The test plan tabular view has been enhanced to also  
    833                                       show test case full text description [[BR]] 
    834  
    835   o Fixed Ticket #10131 and #10217 (Track-Hacks): Deleting a Test Case, deleting Test Catalogs containing Test items. 
    836                                                   This only happened on PosgreSQL. [[BR]] 
    837  
    838   o Fixed some bugs that I found ad which were not reported: 
    839     - The quick search in test catalogs was not working. 
    840     - Indentation of test cases in tabular views for both catalogs and plans was incorrect. 
    841     - Localization (i.e. translation) did not work for some parts of the Administration panel,  
    842       the Statistical charts page and several dialog boxes. 
    843     - Setting a test case status using the pop-up semaphore menu did not work on test plan tabular view. 
    844     - Some more I can't recall :D [[BR]] 
    845  
    846 '''Release 1.4.11 (2012-06-03):''' 
    847   The data referential integrity in case of test catalog, test case and test plan deletion has been enhanced.[[BR]] 
    848   Deleting a test catalog now also deletes all of the contained sub-catalogs, test cases and test plans, as well as the corresponding status change history.[[BR]][[BR]] 
    849   o Fixed Ticket #9857 (Track-Hacks): Deleted test plan is still shown in Test Stats[[BR]] 
    850   o Fixed Ticket #9953 (Track-Hacks): Changing a testcase custom field value gives and error[[BR]] 
    851   o Fixed Ticket #10043 (Track-Hacks): Deleting "zombie" !TestPlans[[BR]] 
    852  
    853 '''Release 1.4.10 (2012-03-03):''' 
    854   o Enhancement #9751 (Track-Hacks): Ability to sort catalogs.[[BR]] 
    855                                      Test Catalogs are now sorted by title in the tree and table views.[[BR]] 
    856   o Fixed Ticket #9776 (Track-Hacks): Testplans not visible with latest Agilo Plugin.[[BR]] 
    857   o Fixed Ticket #9530 (Track-Hacks): Expand all / Collapse all is not running.[[BR]] 
    858                                       This only happened with the Agilo plugin installed.[[BR]] 
    859   o Fixed Ticket #9754 (Track-Hacks): Setting test result seemingly succeeds with expired login.[[BR]] 
    860                                       Now operations such as setting a test case status and updating a custom field,[[BR]] 
    861                                       when failing will display a dialog box with an error message.[[BR]] 
    862   o Fixed Ticket #9758 (Track-Hacks): Can't delete Test Case in v1.4.9.[[BR]] 
    863  
    864 '''Release 1.4.9 (2012-01-04):''' 
    865   o Enhancement #8958 (Track-Hacks): An ability to export test data to CSV format needed.[[BR]] 
    866                                      You can now export to CSV a test catalog or a test plan.[[BR]] 
    867                                      In the test catalog and test plan pages you will find an "Export ..." button.[[BR]] 
    868                                      The export format is designed to eventually import the stuff back into another Test Manager plugin evironment, as soon as a compatible import feature will be implemented :D (the current import feature is simpler than that.)[[BR]] 
    869   o Enhancement #9287 (Track-Hacks): New browser tab for existing testcases. Now you have an option in trac.ini to choose what[[BR]] 
    870                                      to do when clicking on a test case in the catalog/plan. [[BR]] 
    871                                      The default is to NOT open it in a new window, but you can change that from the admin panel,[[BR]] 
    872                                      under Testmanage->Settings, or directly in the trac.ini file like this:[[BR]] 
    873 {{{ 
    874 [testmanager] 
    875 testcase.open_new_window = True 
    876 }}} 
    877   o Fixed Ticket #9297 (Track-Hacks): Can't print testplan table overview. There was a problem with the default print css from Trac.[[BR]] 
    878   o Fixed Ticket #9510 (Track-Hacks): !TestStats for single Testplans at 1.4.8 not working - patched. [[BR]] 
    879                                       Thanks so much Andreas for finding it and for patching it!!! [[BR]] 
    880   o Fixed Ticket #9530 (Track-Hacks): Expand all / Collapse all is not running[[BR]] 
    881   o Fixed Ticket #9654 (Track-Hacks): Error when creating test plans[[BR]] 
    882  
    883 '''Release 1.4.8 (2011-10-23):''' 
    884   o Strongly enhanced the upgrade mechanism. Now it's more robust, should work with all the databases and between arbitrary Test Manager versions.[[BR]] 
    885     The only drawback is that upgrade is only supported from 1.4.7, not from previous versions.[[BR]] 
    886   o Enhancement #9077 (Track-Hacks): Ability to separate and report on test plans by product[[BR]] 
    887   o Enhancement #9208 (Track-Hacks): Test plan with only selected test cases from the catalog, take snapshot version of test cases.[[BR]] 
    888                                      This is an important one. Many users were asking for a way of including only selected test cases into[[BR]] 
    889                                      a Test Plan, for different reasons. Now you have it :D [[BR]] 
    890   o Added French language catalog! Thanks to someone who doesn't want to be cited :D [[BR]] 
    891   o Added [wiki:TestManagerForTracPlugin#TestArtifactChangeHistory Object change history] view. It shows the change history of standard and, more interestingly, custom properties of any test artifact. 
    892   o Fixed Ticket #9141 (Track-Hacks): Update installation 1.4.6 -> 1.4.7 not possible[[BR]] 
    893   o Fixed Ticket #9167 (Track-Hacks): installation of 1.4.7 with postgres database not possible[[BR]] 
    894   o Fixed Ticket #9187 (Track-Hacks): Current test status report should consider only last result of a testcase in the plan. [[BR]] 
    895                                       Thanks to Andreas for his contribution to fixing this one! [[BR]] 
    896 '''Release 1.4.7''' (2011-08-28): 
    897   o Enhancement #8907 (Track-Hacks): Add template for "New !TestCase" - Thanks a lot to Christian for the hard work on this enhancement!!! [[BR]] 
    898                                      Now you can define templates for your new test catalogs and new test cases, and assign default templates based 
    899                                      on each test catalog! [[BR]] 
    900   o Enhancement #8908 (Track-Hacks): Possiblity to change test case status from the tree view.[[BR]] 
    901                                      No more need to open each test case in a plan to set its result, you can now do this directly from the tree view! [[BR]] 
    902   o Fixed Ticket #8869 (Track-Hacks): Loading of Test Manager takes too long and sometimes time out[[BR]] 
    903   o Added Spanish and German catalogs! Thanks a lot to Christian and Andreas for the translations!!! Italian was already part of the plugin.[[BR]] 
    904  
    905 '''Release 1.4.6''' (2011-06-19): 
    906   o Fixed Ticket #8871 (Track-Hacks): No # allowed at custom fields[[BR]] 
    907   o Fixed Ticket #8873 (Track-Hacks): css styles ar not compatible with the agilo plugin[[BR]] 
    908   o Fixed Ticket #8876 (Track-Hacks): Can't create Catalogs/Test cases when trac runs from site root[[BR]] 
    909   o Fixed Ticket #8878 (Track-Hacks): TestManagerForTracPlugin does not play well with MenusPlugin[[BR]] 
    910   o Fixed Ticket #8898 (Track-Hacks): yui_base_url not honored in templates ? [[BR]] 
    911   o Enhancement #8875 (Track-Hacks): More visibility for Tickets related to test suites[[BR]] 
    912   Added more statistical charts, including Current test status pie chart and Tickets related to test cases trend chart[[BR]] 
    913   Simplified setting the outcome of a test case[[BR]] 
    914  
    915 '''Release 1.4.5''' (2011-05-21): 
    916   o Enhancement #8825 (Track-Hacks): Ability to import test cases from Excel (CSV) file[[BR]] 
    917  
    918 '''Release 1.4.4''' (2011-03-11): 
    919   o Fixed Ticket #8567 (Track-Hacks): Javascript error when deleting test plans[[BR]] 
    920   o Enhancement #8596 (Track-Hacks): Remove hard dependency on XML RPC plugin for Trac 0.11[[BR]] 
    921   o Enhancement #8761 (Track-Hacks): Copy multiple test cases into another catalog[[BR]] 
    922   Added wiki documentation for '''copying multiple test cases into another catalog'''. 
    923  
    924 '''Release 1.4.3''' (2011-01-20): 
    925   o Enhancement #8427 (Track-Hacks): Add XML-RPC complete interface for remote management of test objects[[BR]] 
    926   Added wiki documentation for '''[wiki:TestManagerForTracPluginRPCApi the new XML-RPC API]'''. 
    927  
    928 '''Release 1.4.2''' (2011-01-09): 
    929   o Fixed Ticket #8378 (Track-Hacks): Set date and time format correctly in Test Stats page[[BR]] 
    930   Also added support for custom test case outcomes in the Test Stats page[[BR]] 
    931   Added Wiki documentation on the ability to customize the test case outcomes (i.e. states, verdicts) and to link Tickets to Test Cases. 
    932  
    933 '''Release 1.4.1''' (2010-12-27): 
    934   o Enhancement #7486 (Track-Hacks): Customizable test case outcomes (aka verdicts)[[BR]] 
    935   o Enhancement #7570 (Track-Hacks): Add a relationship table between tickets and test cases in plan, and corresponding API[[BR]] 
    936   o Added wiki documentation on the '''[wiki:TestManagerForTracPluginGenericClass Generic Persistent Class framework]''' [[BR]] 
    937  
    938 '''Release 1.3.12''' (2010-12-19): 
    939   o Enhancement #8321 (Track-Hacks): Add standard internationalization support (i18n)[[BR]] 
    940   o Enhancement #8322 (Track-Hacks): Show timestamps according to User's locale[[BR]] 
    941   o Fixed Ticket #8323 (Track-Hacks): Unable to expand Available plans and Test case status change history collapsable sections[[BR]] 
    942  
    943 '''Release 1.3.11''' (2010-12-02): 
    944   o Added out of the box operation to workflow engine: set_owner and set_owner_to_self[[BR]] 
    945   o Enhancement #8259 (Track-Hacks): Add navigation from a test case to its related tickets[[BR]] 
    946  
    947 '''Release 1.3.10''' (2010-11-28): 
    948   o Fixed Ticket #8154 (Track-Hacks): !LookupError: unknown encoding: cp0[[BR]] 
    949  
    950 '''Release 1.3.9''' (2010-11-23): 
    951   o Fixed Ticket #8144 (Track-Hacks): Test statistical charts don't show successful and failed figures[[BR]] 
    952  
    953 '''Release 1.3.8''' (2010-11-23): 
    954   o Fixed Ticket #8121 (Track-Hacks): Catalog Wiki Page not added[[BR]] 
    955   o Fixed Ticket #8123 (Track-Hacks): Can't move testcase more than one time into different catalog[[BR]] 
    956   o Fixed Ticket #8124 (Track-Hacks): !AttributeError: '!NoneType' object has no attribute 'splitlines'[[BR]] 
    957   o Fixed Ticket #8125 (Track-Hacks): "duplicate test case" does not work for previously moved test case[[BR]] 
    958  
    959 '''Release 1.3.7''' (2010-11-20): 
    960   o Enhancement #7704 (Track-Hacks): Add ability to delete a Test Plan[[BR]] 
    961   o Fixed Ticket #8084 (Track-Hacks): Ordering issue[[BR]] 
    962  
    963 '''Release 1.3.6''' (2010-11-09): 
    964   o Fixed Ticket #8004 (Track-Hacks): Cannot search if an admin[[BR]] 
    965  
    966 '''Release 1.3.5''' (2010-10-17): 
    967   o Restored compatibility with Trac 0.11. Now again both 0.11 and 0.12 are supported.[[BR]] 
    968 [[BR]][[BR]] 
    969  
    970 == Author/Contributors == 
    971  
    972 '''Author:''' [wiki:seccanj] [[BR]] 
    973 '''Maintainer:''' [wiki:seccanj] [[BR]] 
    974 '''Contributors:''' 
     779 
     780See the '''[wiki:TestManagerForTracPluginChangeHistory complete list of changes]'''. 
     781 
     782== !Author/Contributors == 
     783'''Author:''' [wiki:seccanj] [[BR]] '''Maintainer:''' [wiki:seccanj] [[BR]] '''Contributors:'''