Page 166 - SOFTWARE TESTING & QUALITY ASSURANCE

Unit 11: Test Case Planning

4. Test Case Identification: These are high-level descriptions and references to the specific test cases
that will be used to check the feature. It should list the selected equivalence partitions and
provide references to the test cases and test procedures used to run them.

Table 11.1 Shows a sample Test Case Identification

Table 11.1 A Sample Test Case Identification

Identification Number
Test Case Description
Check the highest possible value Test Case ID# 17622

Check the lowest possible value Test Case ID# 17623
Check several interim powers of 2 Test Case ID# 17624

It is important that the actual test case values are not defined in this section. For someone
reviewing the test design specifications for proper test coverage, a description of the equivalence
partitions is much more useful than the specific values themselves.
5. Pass/Fail Criteria: This describes exactly what constitutes a pass and a fail of the tested feature.
What is acceptable and what is not? The criteria followed is as given:
(a) A pass is when all the test cases are run without finding a bug.

(b) A case of failure of test condition happens when 10% or more of the test cases fail.
However, there must be a clear criteria based on which the pass or fail of a feature is determined.
11.1.3 Writing Test Cases

IEEE 829 states that the test case specification “documents the actual values used for input along with
the anticipated outputs. A test case also identifies any constraints on the test procedure resulting from
use of that specific test case.”
Fundamentally, the details of a test case should explain exactly what values or conditions will be given
to the software and what result is expected. It can be referenced by one or more test design
specifications or may reference more than one test procedure. The IEEE 829 standard also lists some
additional information that needs to be included.
1. Identifiers: A unique identifier is referenced by the test design specifications and the test
procedure specifications.
2. Test Item: This describes the detailed feature, code module, and so on that's being tested. It
should be more specific than the features listed in the test design specification.

If the test design specification states: ”the addition function of Calculator,” then
the test case specification would state that the upper limit overflow handling of
addition calculations.

It should also provide references to product specifications or other design documents on which the test
case was based.
3. Input Specification: This specification lists all the inputs or conditions given to the software to
execute the test case.

LOVELY PROFESSIONAL UNIVERSITY 159