A test case specifies the conditions that must be validated to enable an assessment of aspects of the system under
test. A test case is more formal than a test idea; typically, a test case takes the form of a specification. In less
formal environments, you can create test cases by identifying a unique ID, name, associated test data, and expected
results.
Test cases can be derived from many sources, and typically include a subset of the requirements (such as use cases,
performance characteristics, and reliability concerns) and other types of quality attributes. For more information on
types of tests and their relationships to quality test attributes, see Concept: Testing Qualitative Requirements.
1. Test Case Description
A description of the purpose or objective of the test, the scope, and any preconditions of the test
2. Execution Condition
A description of a condition that will be exercised during this test
a. Preconditions
For each execution condition, describe the required state that the system should be in before the test can commence.
b. Test Inputs
For each execution condition, enumerate a list of the specific stimuli to be applied during the test. This is generally
referred to as the Inputs to the test, and includes the objects or fields interacted with (and the specific data
values entered) when executing this Test Case.
c. Observation Points
During the test execution, enumerate what specific observations should be made.
d. Control Points
During the test execution, identify any points where the flow of control may alter or vary.
e. Expected Results
The resulting state or observable conditions that are expected as a result of the test having been executed. This may
cover both positive and negative responses (such as error conditions and failures).
f. Postconditions
For each execution condition, describe the required state that the system should be returned to, allowing
subsequent tests to be performed.