Test Step

Go up to Terms and Definitions

A Test Step specifies one action or validation performed as part of a Test Sequence.

As a Sequenced Test Object, a Test Step can contain or reference a Test Sequence that decomposes the Test Step into subordinate Test Steps or Test Executables.

A Test Step can specify an action that:

• Creates a Data Object
• Submits a transaction
• Sends or receives a message
• Invokes an operation
• Changes a configuration
• Changes a network condition
• Changes a state
• Advances or modifies time
• Starts or stops a Node
• Introduces a fault
• Retrieves information
• Captures Evidence

A Test Step can specify a validation that:

• Observes a value
• Observes a state
• Observes a state transition
• Evaluates a condition
• Compares an observed value with an Expected Result
• Confirms an event
• Confirms the absence of an event
• Confirms satisfaction of an evaluation criterion
• Produces a Test Result

A Test Step can identify:

• Its identity
• Its name
• Its description
• Its version
• Its action or validation
• Its applicable Test Items
• Its applicable Test Environments
• Its Test Arguments
• Its Test Argument Values
• Its Expected Results
• Its completion condition
• Its failure condition
• Its timeout
• Its applicable Governance Policies
• Its Provenance
• Its Traceability

A Sequence Step identifies the occurrence of a Test Step at a particular position in a Test Sequence. The same Test Step can participate in multiple Test Sequences or occur more than once within the same Test Sequence.

Sequenced Test Object that specifies one action or validation performed as part of a Test Sequence

Adapted from:

• OMG Test Information Interchange Format (TestIF), Version 1.0 Beta 3, Section 7.3.16, TestStep
• Test Object
• Sequenced Test Object
• Test Case
• Test Sequence
• Sequence Step
• DIDO Reference Implementation Conceptual Model
• DIDO-TE draft Requirements Register

OMG TestIF defines TestStep as an action or validation performed as part of a Test Sequence. TestIF permits Test Steps to contain other Test Steps so that a Test Step can decompose a larger action or validation.

Every Test Step is a Sequenced Test Object and therefore a Test Object.

A Test Step differs from a Sequence Step:

• A Test Step specifies a reusable action or validation
• A Sequence Step identifies an occurrence of a Sequenced Test Object at a position within a Test Sequence

A Test Step differs from a Test Case:

• A Test Step specifies one action or validation
• A Test Case specifies the Test Steps and Expected Results used to verify a defined subject

A Test Step differs from a Test Executable:

• A Test Step specifies an action or validation independently of a particular execution mechanism
• A Test Executable contains or references low-level procedural or executable information used to automate an action or validation

A Test Step differs from a Test Result:

• A Test Step specifies the action or validation to perform
• A Test Result records the outcome produced by performing the Test Step

A Test Step can have one or more Expected Results when the action or validation produces or evaluates multiple independently identified outcomes.

A Test Step can be performed manually or automatically. The Test Step definition remains independent of the execution mechanism.

A change to the action, validation, Expected Results, completion condition, failure condition, or timeout can create a new Test Step version when the change affects Test Execution, reproducibility, comparison, or validation.

A DIDO-TE Test Case verifies a proposed DIDO state transition.

One Test Step submits a proposed transaction to a participating Node.

Another Test Step observes the resulting DIDO state and compares it with the applicable Expected Result.

The Test Sequence uses separate Sequence Steps to identify the order in which the two Test Steps occur.

During Test Execution, the Test Run records the Test Result associated with each executed Test Step.