Executed Sequence Step

Go up to Terms and Definitions

A Sequence Step identifies a planned occurrence of a Sequenced Test Object within a Test Sequence.

When a Sequence Step is performed, an execution occurrence exists within the applicable Test Run. This occurrence is an Executed Sequence Step.

A Sequence Step can be performed more than once during a Test Run. Each performance constitutes a separate Executed Sequence Step. This separation allows the runtime argument values, timing, status, observations, and Test Results associated with each occurrence to remain distinguishable.

occurrence of a sequence step performed during a test run

* OMG Test Information Interchange Format (TestIF), Version 1.0, Test Run, Test Sequence, Sequence Step, and Sequenced Test Object concepts * DIDO-TE Section 6.3.2, Executed Sequence Step

Executed Sequence Step is a DIDO-TE term derived from the TestIF execution and sequencing model. TestIF does not define a class named ExecutedSequenceStep.

An Executed Sequence Step is distinct from:

* the definition-side Sequence Step * the reusable Sequenced Test Object referenced by the Sequence Step * the act that initiates or controls Test Execution * the Test Run containing the occurrence * a Test Result produced or collected during the occurrence

Information associated with an Executed Sequence Step can include:

* occurrence identity * the governing Sequence Step * runtime argument values * start and completion times with their applicable time bases * execution status * observations and Test Results * Provenance * Traceability

A Test Sequence contains a Sequence Step that references a connectivity Test Case. During a Test Run, the Sequence Step is performed three times using different runtime argument values.

The three performances constitute three Executed Sequence Steps. Each Executed Sequence Step refers to the same definition-side Sequence Step but has its own occurrence identity, runtime values, timing, status, and Test Results.

—