Changes between Version 33 and Version 34 of TestManagerForTracPlugin


Ignore:
Timestamp:
Oct 6, 2010, 2:50:10 PM (14 years ago)
Author:
Roberto Longobardi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestManagerForTracPlugin

    v33 v34  
    4343Notice at the top of the page breadcrumbs to easily navigate up in the catalogs tree.
    4444
     45You 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
     46The former is useful to actually work on the Test Catalog, adding sub-catalogs and new test cases, or modifying them.
     47The 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.
     48
    4549You 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.
    4650
     
    6064[[Image(screen2.JPG)]]
    6165[[BR]]
    62 [[BR]]
     66'''Tree View of the Test Catalog'''
     67[[BR]]
     68[[BR]]
     69[[Image(screen13.png)]]
     70[[BR]]
     71'''Tabular view of the Test Catalog'''
     72[[BR]]
     73[[BR]]
     74
    6375== Test Cases ==
    6476Test Cases are the smallest units of test execution.
     
    116128To 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".
    117129
    118 The 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.
     130The new Test Plan will be opened for display, showing all of the Test Cases in the catalog, in the "Untested" status.
     131
     132As with Test Catalogs, you can '''choose between tree-like and a tabular representation''' of the Test Plan, as shown in the figures below.
     133The former is useful to actually work on the Test Plan and to view test cases before actually going and executing them.
     134The 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.
    119135
    120136[[BR]]
    121137[[BR]]
    122138[[Image(screen7.JPG)]]
     139[[BR]]
     140'''Tree View of the Test Plan'''
     141[[BR]]
     142[[BR]]
     143[[Image(screen14.png)]]
     144[[BR]]
     145'''Tabular view of the Test Plan'''
    123146[[BR]]
    124147[[BR]]