public:99_annexes:annex-b-terms-and-definitions:e:executed_sequence_step

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:99_annexes:annex-b-terms-and-definitions:e:executed_sequence_step [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:e:executed_sequence_step [2026/09/13 17:06] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Executed Sequence Step ======
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A [[public:99_annexes:annex-b-terms-and-definitions:s:sequence_step|Sequence Step]] identifies a planned occurrence of a [[public:99_annexes:annex-b-terms-and-definitions:s:sequenced_test_object|Sequenced Test Object]] within a [[public:99_annexes:annex-b-terms-and-definitions:t:test_sequence|Test Sequence]].
 +
 +When a Sequence Step is performed, an execution occurrence exists within the applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test_run|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 [[public:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] associated with each occurrence to remain distinguishable.
 +
 +===== Definition =====
 +
 +occurrence of a [[public:99_annexes:annex-b-terms-and-definitions:s:sequence_step|sequence step]] performed during a [[public:99_annexes:annex-b-terms-and-definitions:t:test_run|test run]]
 +
 +===== Source =====
 +
 +* [[https://www.omg.org/spec/TestIF/1.0/PDF|OMG Test Information Interchange Format (TestIF), Version 1.0]], Test Run, Test Sequence, Sequence Step, and Sequenced Test Object concepts
 +* [[private:07-dido-te:06-information-model:06-03-test-execution:06-03-02-executed-sequence-step|DIDO-TE Section 6.3.2, Executed Sequence Step]]
 +
 +===== Note =====
 +
 +Executed Sequence Step is a [[public:99_annexes:annex-b-terms-and-definitions:d:dido-te|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 [[public:99_annexes:annex-b-terms-and-definitions:t:test_execution|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
 +* [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
 +* [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +===== Example =====
 +
 +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.
 +
 +---
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>