Test Case
Discussion
A Test Case specifies the Test Steps and Expected Results used to verify a defined subject.
As a Sequenced Test Object, a Test Case can contain or reference a Test Sequence. The Test Sequence establishes the order and progression of the Sequence Steps associated with the Test Case.
A Test Case can identify:
-
Its identity
-
Its name
-
Its Test Purpose
-
Its version
-
The subject being verified
-
The applicable Test Items
-
The applicable System Under Test
-
The applicable Test Environments
-
The applicable Test Sequence
-
The applicable Test Steps
-
The applicable Test Executables
-
The applicable Test Arguments
-
The applicable Test Argument Values
-
The applicable Expected Results
-
The applicable entry conditions
-
The applicable completion conditions
-
The applicable evaluation criteria
-
The applicable Governance Policies
-
Its Provenance
-
Its Traceability
A Test Case can participate in one or more Test Sets.
A Test Case can reference reusable Test Steps and Test Executables without containing copies of them. Each Sequence Step identifies the occurrence of a Test Step or Test Executable within the Test Sequence.
Definition
Sequenced Test Object that specifies the Test Steps and Expected Results used to verify a defined subject
Source
Adapted from:
-
DIDO Reference Implementation Conceptual Model
-
DIDO-TE draft Requirements Register
OMG TestIF defines TestCase as the set of steps necessary to verify something. TestIF permits a Test Case to contain any number of Test Steps organized through a Test Sequence.
This definition preserves the TestIF verification purpose while identifying both Test Steps and Expected Results as essential characteristics of a Test Case.
Note
Every Test Case is a Sequenced Test Object and therefore a Test Object.
A Test Case differs from a Test Set:
-
A Test Case specifies the Test Steps and Expected Results used to verify a defined subject
-
A Test Set groups related Test Objects for a defined Test Purpose
A Test Case differs from a Test Step:
-
A Test Case identifies the complete verification unit
-
A Test Step identifies one action or validation performed as part of a Test Sequence
A Test Case differs from a Test Executable:
-
A Test Case specifies what the Test verifies
-
A Test Executable contains or references low-level procedural or executable information used for automated Test Execution
A Test Case differs from a Test Result:
-
A Test Case specifies the verification to perform
-
A Test Result records an outcome produced by Test Execution
A Test Case differs from a Test Run:
-
A Test Case specifies the verification unit
-
A Test Run records an identified execution and its Test Results
A Test Case can reference more than one Test Item. The applicable Test Definition identifies which Test Item or collection of Test Items constitutes the subject being verified.
A change to the Test Purpose, Test Steps, Test Sequence, Expected Results, or evaluation criteria can create a new Test Case version when the change affects Test Execution, reproducibility, comparison, or validation.
Example
A DIDO-TE Test Case verifies that a proposed DIDO transaction produces the required successor state.
The Test Case references:
-
The applicable Test Items
-
The applicable Test Environment
-
A Test Step that submits the transaction
-
A Test Step that observes transaction distribution
-
A Test Step that observes validation by the participating Nodes
-
A Test Step that retrieves the resulting DIDO state
-
An Expected Result identifying the required successor state
During Test Execution, the Test Run records the Test Case version, execution context, and resulting Test Results.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.