Test Cases Planning
and methodically planning test
cases is a step in that direction. Doing so is
very important for four reasons:
Proof of testing (or not testing).
829 states that the test design
specification "refines the test approach
[defined in the test plan] and identifies the
features to be covered by the design and its
associated tests. It also identifies the test
cases and test procedures, if any, required to
accomplish the testing and specifies the
feature pass/fail criteria."
the details of a test case should explain exactly what
values or conditions will be sent to the software and
what result is expected:
The IEEE 829 standard also lists some other
important information that should be included:
Identifiers. A unique identifier is referenced by the test
design specs and the test procedure specs.
Test item. This describes the detailed feature, code
module, and so on that's being tested.
Input specification. This specification lists all the inputs or
conditions given to the software to execute the test case.
Output specification. This describes the result you expect
from executing the test case.
Environmental needs. Environmental needs are the
hardware, software, test tools, facilities, staff, and so on that
are necessary to run the test case.
Special procedural requirements. This section describes
anything unusual that must be done to perform the test.
Inter-case dependencies. If a test case depends on
another test case or might be affected by another, that
information should go here.
829 states that the test procedure
"identifies all the steps required to operate
the system and exercise the specified test
cases in order to implement the associated
step-by-step details of exactly how to
perform the test cases:
Identifier. A unique identifier that ties the test
procedure to the associated test cases and test
Purpose. The purpose of the procedure and
reference to the test cases that it will execute.
Special requirements. Other procedures, special
testing skills, or special equipment needed to run
Procedure steps. Detailed description of how the tests are
to be run:
Log. Tells how and by what method the results and observations will
Setup. Explains how to prepare for the test.
Start. Explains the steps used to start the test.
Procedure. Describes the steps used to run the tests.
Measure. Describes how the results are to be determined for example,
with a stopwatch or visual determination.
Shut down. Explains the steps for suspending the test for unexpected
Restart. Tells the tester how to pick up the test at a certain point if
there's a failure or after shutting down.
Stop. Describes the steps for an orderly halt to the test.
Wrap up. Explains how to restore the environment to its pre-test
Contingencies. Explains what to do if things don't go as planned.