Changes between Version 18 and Version 19 of TestManagerForTracPlugin


Ignore:
Timestamp:
Aug 18, 2010, 1:22:30 PM (4 years ago)
Author:
seccanj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestManagerForTracPlugin

    v18 v19  
    55== Description ==
    66
    7 A Trac plugin to create Test Cases, organize them in catalogs and track their execution status and outcome.
     7A Trac plugin to create Test Cases, organize them in Catalogs, generate Test Plans and track their execution status and outcome.
    88
    99Differently 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.
     
    1212A 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.
    1313
     14Multiple Test Plans can be associated to any Test Catalog, in order to keep track of the execution of the corresponding Test Cases in a particular testing context.
     15
    1416Here follows an overview of the plugin functionalities. For a full tutorial, refer to the powerpoint presentations attached below (the ones with shorter names work).
    1517
     
    1719[[BR]]
    1820== Test Catalogs ==
    19 Test catalogs contain sub-catalogs or Test Cases. A Javascript tree view displays a catalog node and its sub-tree, including the test cases and their status.
     21Test 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.
    2022
    21 Next to each catalog a number in brackets shows the number of test cases it contains.
     23Next to each catalog (or sub-catalog) a number in brackets shows the number of test cases it contains.
    2224
    2325Notice at the top of the page breadcrumbs to easily navigate up in the catalogs tree.
     
    2628Be careful that the first line will always be taken as the title of the catalog (the same stands for test cases, read below).
    2729
    28 Just save the new page ("Submit Changes") and you'll have your new catalog in place.
     30Just save the new page ("Submit Changes") and you'll have your new (sub-)catalog in place.
    2931
    3032[[BR]]
     
    3840They are implemented again as wiki pages, with a naming convention that allows the plugin code to recognize them and treat them appropriately.
    3941
    40 You can track the execution status a Test Case by simply clicking on the corresponding light in the semaphore at the bottom of the page.
    41 
    42 You don't need to save anything, the change is immediately recorded in the database by means of an Ajax call (you may even envision calling this RESTful API from external applications).
    43 
    4442Again, notice the breadcrumbs at the top, useful to go back to the enclosing catalog or any catalog up the hierarchy.
    4543
     
    4947[[BR]]
    5048[[BR]]
    51 == Searching and filtering Test Cases in the tree view ==
     49== Moving Test Cases from one catalog to another ==
    5250
    5351It is also possible to move a Test Case into a different catalog, with an experience similar to cut&paste.
     
    5755You then navigate and open the destination catalog and click on "Move the copied Test Case here" button (which only appears if a Test Case has been cut first).
    5856
    59 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.
     57It 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.
    6058
    6159[[BR]]
     
    6462[[BR]]
    6563[[BR]]
    66 == Searching anf filtering Test Cases in the tree view ==
     64== Test Plans ==
     65A Test Plan represents a plan for a particular execution of all the Test Cases in a Test Catalog (or sub-catalog).
     66
     67Think for example at the build verification test following a nightly build, or, for traditional projects, Technical Test and eventually Client Test.
     68
     69Thus 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.
     70The 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.
     71
     72[[BR]]
     73[[BR]]
     74[[Image(screen9.JPG)]]
     75[[BR]]
     76[[BR]]
     77
     78To 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".
     79
     80The new Test Plan will be opened for display, showing all of the Test Cases in the catalog, in the "Untested" status, as shown in the figure below.
     81
     82[[BR]]
     83[[BR]]
     84[[Image(screen7.JPG)]]
     85[[BR]]
     86[[BR]]
     87
     88To track the execution status of a Test Case in a particular Test Plan, open it by clicking on the Test Case name from the Test Plan tree.
     89Then simply click on the corresponding light in the semaphore at the bottom of the page, as shown in the following figure.
     90
     91You don't need to save anything, the change is immediately recorded in the database by means of an Ajax call (this API will be documented asap, to allow for setting test case execution status from external applications).
     92
     93The change is immediately reflected in the Test Plan.
     94
     95[[BR]]
     96[[BR]]
     97[[Image(screen8.JPG)]]
     98[[BR]]
     99[[BR]]
     100
     101When viewing a Test Case, you can open a new Ticket by means of the "Open Ticket on this Test Case" button.
     102
     103The 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.
     104
     105This 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:
     106
     107 * testCaseNumber: The wiki page for the corresponding Test Case
     108 * planId: The ID of the Test Plan
     109 * planName: The name of the Test Plan
     110
     111For example, to get the test case number, you template will have something like:
     112{{{
     113  bleah bleah
     114  Test Case: %(testCaseNumber)s
     115  bleah bleah
     116}}}
     117
     118== Searching and filtering Test Cases in the tree view ==
    67119A 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.
     120
     121This is available both in the context of a Test Catalog and in Test Plans.
    68122
    69123Multiple words (or parts of) separated by blanks are supported, in AND condition.
    70124
    71 You can also add a test case status to filter by this criterion.
     125In the case of a Test Plan, you can also add a test case status to filter by this criterion.
    72126The supported statuses are (even substrings of):
    73127 * untested
     
    82136[[BR]]
    83137
    84 Tutorial (as powerpoint presentation):
     138== Security ==
     139
     140The following new permissions are available to manage the Test Manager security:
     141
     142 * TEST_VIEW - Ability to view test catalogs and test cases
     143 * TEST_MODIFY - Ability to create and edit test catalogs and test cases
     144 * TEST_EXECUTE - Ability to change the status of a test case in a test plan
     145 * TEST_DELETE - Ability to delete test cases
     146 * TEST_PLAN_ADMIN - Ability to generate and delete test plans
     147
     148
     149== Tutorial (as powerpoint presentation) ==
    85150 * attachment:"UserGuide_part_1.ppt"
    86151 * attachment:"UserGuide_part_2.ppt"
    87152 * attachment:"UserGuide_part_3.ppt"
    88153
     154
     155== Project site ==
    89156Project site: http://sourceforge.net/projects/testman4trac/
    90157
     158The project is also on Pypi: http://pypi.python.org/pypi/TestManager
    91159
    92160== Bugs/Feature Requests ==