Glossary terms

1.
2.
3.
4.
5.
6.
7.
8.
9.

test condition
test case / test case specification
test procedure
test script
test design / test design specification
test procedure specification
test data
Traceability
IEEE 829

test condition
An item or event of a component or system that could be
verified by one or more test cases, e.g. a function,
transaction, feature, quality attribute, or structural
element.
(test requirements, test inventory, test possibilities)
For example:
We have to test a field accepts integer value from 1 to 100, there
are test conditions:
Not integer: text , double, (invalid)
Integer value less than 1 (invalid)
Integer value grater than 100 (invalid)
Integer value from 1 to 100 (valid)

test case
A set of input values, execution preconditions,
expected results and execution post conditions,
developed for a particular objective or test
condition, such as to exercise a particular program
path or to verify compliance with a specific
requirement. [After IEEE 610]
What is the difference between test condition
and test case?
A test condition is general, a test case is specific for 1 or
more test conditions
A test condition can be implemented to 1 or more test
cases

test case specification

A document specifying a set of test
cases (objective, inputs, test actions,
expected results, and execution
preconditions) for a test item. [After
IEEE 829]
Note:
Document should follow IEEE 829

test procedure specification

A document specifying a sequence of
actions for the execution of a test.
Also known as test script or manual
test script. [After IEEE 829]

test script
Commonly used to refer to a test
procedure specification, especially an
automated one.

test design specification

A document specifying the test
conditions (coverage items) for a test
item, the detailed test approach and
identifying the associated high level
test cases. [After IEEE 829]

test design
(1) See test design specification.
(2) The process of transforming
general testing objectives into
tangible test conditions and test
cases.

test data
Data that exists (for example, in a
database) before a test is executed,
and that affects or is affected by the
component or system under test.

traceability
The ability to identify related items in
documentation and software, such as
requirements with associated tests.
See also horizontal traceability,
vertical traceability.

In other word, able to be linked back to test basis

Why is traceability important? - When requirements
change, we can identify which test cases should be
removed or modified.

IEEE 829

IEEE 829:1998. Standard for Software

Test Documentation.

IEEE 829

Test
condition
Test
condition

Test
condition
Test
condition

Test
case
Test
case

Test
case
Test
case

Test
procedure
Test
procedure

Test
procedure
Test
procedure

documented

Test
design
specificati
on

Test case
specification

Test
procedure
specificati
on