Test Planning - Software Testing: Testing Across the Entire Software Development Life Cycle - page 85

9.
10.
11.

test closedown procedure
test reset procedure for rerun

test execution steps
(a). step number
(b). step action
(c). expected results
(d).

Repeated

Placeholder actual results

12.
13.
14.
15.

Placeholder fi rst attempt to execute this test case date: time

Placeholder number of attempts to successfully execute this test case

Placeholder list of software defects discovered by this test case

Placeholder is this test case executed successfully ? (yes/no)

<Placeholder>

Some of the items above are prefi xed by <Placeholder>. This denotes the need
for some type of tracking and reporting capability to provide that item from external
sources. Some test teams opt to do this tracking and reporting with simple tools like
spreadsheets or simple databases. Other test teams opt to do this tracking and re-
porting with more complex test management tools. At the end of the testing day, the
approach you choose must tell you in detail what testing was attempted, what testing
succeeded, and what testing failed.

Here is a brief description of each test case item:

1. Unique test case ID — a string of letters and numbers that uniquely identify

this test case document. The ID is defined during test plan design and is en-
tered on test plan item 9(d).
Unique title —a short descriptive label that clearly implies the purpose of this
test case. The title is defined during test plan design and is entered on test
plan item 9(d) beside the test case ID.
Brief description —a paragraph that expands on the title to give more details
about the purpose of this test case. The description is defined during test plan de-
sign and is entered on test plan item 9(d) beside the test case ID and unique title.
Development phase in which this test case is executed —this is a cross-
reference to the development phase section of the test plan that mentions this
test case. It is meant to be a reminder of the development state of the code to
be tested as a reality check against the kind of testing this test case is intended
to accomplish.
Specific testing goals and their achievement measures —this item takes the
purpose of the test case stated in the title and brief description and quantifies
specific testing goals as well as how the test team can measure the achieve-
ment of these goals.

2.

3.

4.

5.