Chapter 5: Test Management

<< Previous Chapter | Table of Contents | Next Chapter >>

Test Cases

The testing phase of a project involves creating test cases and exercising them in order to identify defects. Each test case provides instructions for performing a test, and a clear description of the expected result. The test cases for a project collectively constitute a test plan. As each test case is executed, its outcome (as success or failure) is recorded. For each failed test, one or more issues (defects) are raised.

When you select the Test Management node, a search screen is displayed. You can search for a test case either by its ID, or a set of other search criteria. To search by ID, choose 'By ID' from the Search drop-down list and enter the test case ID in the ID field. Alternatively, select 'By Criteria' from the Search drop-down list. In this case, you can search using Business Unit, Stage, Title, Instructions, Project, Module, Priority, Category, Type, or Phase fields.

If you leave this blank, a wild-card search is performed, which will return all test cases. Press Find to perform your search. The search result is displayed in the table below the search criteria.

Provided that you have the relevant permissions, you can:

The Graphical View tab displays the search result as a pie chart.

The pie chart can be organized in terms of test case Category, Type, Phase, or Priority, as denoted by the View By drop-down list. You can view the test cases represented by each pie chart segment by clicking on that segment. You will be asked if you want those test cases to be added to the navigation tree.


Test Case Details

When you create a test case or view the details of an existing test case, the test case is added to the navigation tree, as a child of the Test Management node.

The Test Case tab displays test case summary information. If you have test case edit permission, you can modify some of these fields. Fields specified as read-only are managed by the system.


Test Runs

The Test Runs tab lists the test runs that have been performed, in tabular format.

For each test run, the ID, the date, the user who performed the test, the build number, the test cycle, the test phase, the outcome, and the number of issues raised are displayed.

To create a new test run, press the Add Run button and enter the details into the dialog displayed.

To delete a test run, select its row and press the Delete Run button.

To view the issues raised for a test run, select its row and press the Show Issues button. The view will change to the Issue Management module and the matching issues will be listed.

To add a new issue to a test run, select its row and press the Add Issue button. A new issue (with correct project, module, build, and type) will be created, added to the Issue Management module, and brought to view.


Attachments

The Attachments tab displays a list of documents attached to the test case, as a table.

This facility may be used to provide additional information (e.g., graphical) about the test case. You should not use it for recording test run outcomes (e.g., failure screen dumps). Such documents should be attached to issues instead.

For each attachment, its File Name and file Size (in bytes) are listed in the table. When an attachment is opened for editing by a user, the username appears in the Locked By column. When an attachment is opened for editing or viewing, the file is retrieved from the database and written to the local disk. The local file's path is displayed in the Local Path column.

You can do the following operations:


<< Previous Chapter | Table of Contents | Next Chapter >>

Copyright 2005 PragSoft Corporation (www.pragsoft.com)