Test Sequence

Go up to Terms and Definitions

A Test Sequence defines the order and progression of Sequenced Test Objects during Test Execution.

A Test Sequence contains one or more Sequence Steps. Each Sequence Step identifies:

• A position within the Test Sequence
• The applicable Sequenced Test Object
• The applicable Test Argument Values
• The Sequence Steps that can follow it
• The conditions governing progression to those Sequence Steps

A Test Sequence can direct the execution of:

• Test Sets
• Test Cases
• Test Steps
• Test Executables

A Test Sequence can define:

• One or more initial Sequence Steps
• Sequential progression
• Parallel progression
• Conditional progression
• Repetition
• Alternative paths
• Error-handling paths
• Completion conditions
• Termination conditions

Progression can depend on:

• Completion of a Sequence Step
• A Test Result
• A Verdict
• A measured value
• An observed event
• A timeout
• An error
• A Governance Policy
• Another defined condition

definition of the order and progression of Sequenced Test Objects during Test Execution

Adapted from:

• OMG Test Information Interchange Format (TestIF), Version 1.0 Beta 3, Sections 7.3.4 and 7.3.14
• Sequence Step
• Sequenced Test Object
• Test Execution
• DIDO Reference Implementation Conceptual Model
• DIDO-TE draft Requirements Register

OMG TestIF defines TestSequence as the class that establishes the order and progression of execution for a series of SequencedTestObjects.

OMG TestIF represents each position in the Test Sequence as a SequenceStep. Each SequenceStep references a SequencedTestObject and identifies the Sequence Steps that can follow it.

A Test Sequence differs from a Sequence Step:

• A Test Sequence defines the overall execution progression
• A Sequence Step identifies one position within that progression

A Test Sequence differs from a Sequenced Test Object:

• A Sequenced Test Object defines reusable test content
• A Test Sequence defines how occurrences of Sequenced Test Objects progress during Test Execution

A Test Sequence differs from Test Execution:

• A Test Sequence defines the planned progression
• Test Execution performs the applicable Sequenced Test Objects according to that progression

A Test Sequence can contain multiple Sequence Steps that reference the same Sequenced Test Object. Each Sequence Step represents a separate occurrence and can supply different Test Argument Values or progression conditions.

Multiple initial Sequence Steps indicate parallel starting paths. Multiple following Sequence Steps can indicate parallel or conditional progression according to the applicable sequence rules.

The structural presence of multiple following Sequence Steps does not by itself determine whether they execute concurrently or conditionally. The Test Sequence must provide sufficient progression information to resolve that behavior.

A Test Sequence does not record what occurred during Test Execution. The applicable Test Run and Test Results record the actual execution path and outcomes.

A Test Sequence evaluates a proposed transaction across a Node Set.

The Test Sequence defines Sequence Steps that:

• Establish the applicable Test Environment
• Submit the proposed transaction
• Observe the response from each applicable Node
• Compare the observed states with the applicable Expected Results
• Collect the supporting Evidence
• Terminate successfully when all required Test Results receive a passing Verdict
• Follow an error-handling path when a required Node fails to respond

The resulting Test Run identifies the Sequence Steps actually performed and the Test Results produced for those steps.