<Project
Name>
Test Case
Version <1.0>
[Note: The following template is provided for use with the
Unified Process for EDUcation. Text
enclosed in square brackets and displayed in blue italics (style=InfoBlue) is
included to provide guidance to the author and should be deleted before
publishing the document. A paragraph entered following this style will
automatically be set to normal (style=Body Text).]
[To customize automatic fields (which display a gray
background when selected), select File>Properties and replace the Title,
Subject and Company fields with the appropriate information for this
document. After closing the dialog,
automatic fields may be updated throughout the document by selecting Edit>Select
All (or Ctrl-A) and pressing F9, or simply click on the field and press
F9. This must be done separately for
Headers and Footers. Alt-F9 will toggle
between displaying the field names and the field contents. See Word help for more information on working
with fields.]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
7. Special procedural requirements
Test Case
This Test Case Specification document for the <Project Name>
defines a test case for an item that should be tested.
[The sections of the test case specification shall be
ordered in the specified sequence. Additional sections may be included at the
end. If some or all of the content of a section is in another document, then a
reference to that material may be listed in place of the corresponding content.
The referenced material must be attached to the test case specification or available
to users of the case specification.].
Specify the unique
identifier assigned to this test case.
Identify and briefly
describe the items and features to be exercised by this test case.
For each item,
consider supplying references to the following test item documentation:
a) Requirements
specification
b) Design
specification
c) Users guide
Specify each input required to execute the test case. Some
of the inputs will be specified by value, while others, such as constant tables
or transaction files, will be specified by name. Identify all appropriate
databases, files, terminal messages, memory resident areas, and values passed
by the operating system.
Specify all required relationships between inputs.
Specify all of the outputs and features required of the test
items. Provide the exact value for each required output or feature.
Specify the
characteristics and configurations of the hardware required to execute this
test
Specify the system
and application software required to execute this test case. This may include
system software such as operating systems, compilers, simulators, and test
tools. In addition, the test item may interact with application software.
Specify any other
requirement.
Describe any special constraints on the test procedures that
execute this test case. These constraints may involve special set up, operator
intervention, output determination procedures, and special wrap up.
List the identifiers of test cases that must be executed
prior to this test case. Summarize the nature of the dependencies.