Chapter 5: Test Management
<< Previous Chapter | Table of Contents | Next Chapter >>
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:
- Clear your search criteria and result by pressing the Clear button.
- Create a new test case by pressing the New button.
- View the details of a test case by selecting its row in the table and pressing the Details
button, or simply double-clicking the row.
- Delete a test case by selecting its row and pressing the Delete button. You will be asked to
confirm this operation.
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
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.
- The Title field displays a descriptive summary for the test case.
- The Archived check box indicates whether the test case has been archived.
- The BU field displays the test case's business unit. When you create a new test case, this is automatically
set to the business unit you're in. This field is read-only, unless you're a user in the SysAdmin group and
the Project field is set to blank.
- The Project field displays the project to which the test case applies.
When you choose another project from the project drop-down list, the BU field is automatically set to
the selected project's BU.
- The Module field displays the project module to which the test case applies.
- The Category field displays the test case category.
- The Type field displays the type of test case.
- The Phase field displays the testing phase for which the test case is intended.
- The Priority field displays the priority of the test case in relation to other test cases.
- The Created By field is automatically set to the user who originally created the test case (read-only).
- The Created On field is automatically set to when the test case was created (read-only).
- The Instructions field describes the steps that need to be undertaken in order to perform the test.
- The Expected Result field describes the expected outcome in order for a test case to pass.
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.
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:
- To attach a new document, press the Attach button. A file navigation dialog is displayed.
Navigate to the desired file and open it. The file is permanently attached to the project.
- To view an attachment, select its row and press the View button. A read-only
copy of the file is written to the disk and opened for viewing using the application associated with the file.
- To modify the contents of an attachment, select its row and press the Edit button.
A writable-copy of the file is written to the local disk and opened for editing using the application associated
with the file. After you've edited the file, close it, and press the Save button to save your
changes to the database, or press the Unlock button to ignore your changed.
- To detach an attachment, select its row and press the Detach button. The file is
removed from the database. However, any local copies are left untouched.
<< Previous Chapter | Table of Contents | Next Chapter >>
Copyright © 2005 PragSoft Corporation (www.pragsoft.com)