Test Run State [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Test Run State ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Test Run State identifies the lifecycle condition of a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] at a particular time.

A Test Run changes from one Test Run State to another in response to lifecycle events occurring during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].

A Test Run State can identify whether the Test Run:

  * Has not started
  * Is ready to start
  * Is running
  * Is paused
  * Completed its defined execution
  * Terminated without completing its defined execution

The standard Test Run States are:

  * **Not Started**
  * **Ready**
  * **Running**
  * **Paused**
  * **Completed**
  * **Terminated**

**Not Started** identifies a Test Run that exists but has not begun Test Execution.

**Ready** identifies a Test Run for which the applicable prerequisites have been satisfied and which can begin Test Execution.

**Running** identifies a Test Run actively performing its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_sequence|Test Sequence]], [[dido:99_annexes:annex-b-terms-and-definitions:s:sequence_step|Sequence Steps]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Steps]], or [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executables]].

**Paused** identifies a Test Run whose Test Execution has temporarily stopped and can resume according to the applicable control rules.

**Completed** identifies a Test Run that satisfied its defined completion condition.

**Terminated** identifies a Test Run that stopped without satisfying its defined completion condition.

A Test Run in the Terminated state has an applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_termination_reason|Test Run Termination Reason]].

A Test Run State can identify:

  * Its name
  * Its description
  * Its entry condition
  * Its exit condition
  * Its permitted preceding states
  * Its permitted following states
  * Its applicable lifecycle events
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]]
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:authority|Authority]]
  * Its recorded time
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

A Test Run record can preserve each Test Run State transition, including:

  * The preceding Test Run State
  * The following Test Run State
  * The event causing the transition
  * The time of the transition
  * The [[dido:99_annexes:annex-b-terms-and-definitions:a:actor|Actor]] requesting or causing the transition
  * The applicable Governance Policies
  * The result of the transition
  * The supporting Evidence

===== Definition =====

//lifecycle condition of a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] at a particular time//

===== Source =====

Adapted from:

  * [[https://www.omg.org/spec/TestIF/1.0/PDF|OMG Test Information Interchange Format (TestIF), Version 1.0]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
  * DIDO Reference Implementation Conceptual Model
  * DIDO-TE draft Requirements Register

OMG TestIF provides Test Run, Test Result, and Verdict concepts for exchanging test information and execution results.

OMG TestIF does not prescribe the DIDO-TE Test Run lifecycle states defined on this page. This definition introduces Test Run State for DIDO-TE operational control, lifecycle management, Evidence, Provenance, and Traceability.

===== Note =====

A Test Run has exactly one current Test Run State at a particular time.

The current Test Run State does not replace the history of Test Run State transitions. A Test Run record can preserve every state occupied by the Test Run and every transition among those states.

A Test Run State differs from a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_termination_reason|Test Run Termination Reason]]:

  * A Test Run State identifies the lifecycle condition of a Test Run
  * A Test Run Termination Reason identifies why a Test Run entered the Terminated state

A Test Run State differs from a [[dido:99_annexes:annex-b-terms-and-definitions:v:verdict|Verdict]]:

  * A Test Run State identifies the lifecycle condition of a Test Run
  * A Verdict expresses an evaluation of a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]]

A Test Run can enter the Completed state and still produce a Test Result assigned a failing Verdict.

A Test Run can enter the Terminated state without producing sufficient Test Results to assign a conclusive Verdict.

The **Completed** state means the Test Run satisfied its defined completion condition. It does not mean:

  * Every Test Result received a passing Verdict
  * The tested system satisfied every applicable [[dido:99_annexes:annex-b-terms-and-definitions:r:requirement|Requirement]]
  * A favorable [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_decision|Validation Decision]] was made
  * No errors or warnings occurred

The **Terminated** state means the Test Run stopped without satisfying its defined completion condition. The applicable Test Run Termination Reason identifies why it stopped.

The **Paused** state differs from the Terminated state because a paused Test Run remains eligible to resume.

The applicable Governance Policies determine:

  * Which Actors can initiate a Test Run
  * Which Actors can pause or resume a Test Run
  * Which Actors can cancel a Test Run
  * Which Test Run State transitions are permitted
  * Which Evidence must be preserved for each transition

===== Example =====

An authorized [[dido:99_annexes:annex-b-terms-and-definitions:u:user|User]] creates a Test Run for a selected [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]].

The Test Run progresses through the following Test Run States:

  * **Not Started** when DIDO-TE creates the Test Run record
  * **Ready** after DIDO-TE confirms the applicable [[dido:99_annexes:annex-b-terms-and-definitions:s:starting_condition|Starting Conditions]]
  * **Running** when Test Execution begins
  * **Paused** when an authorized User requests a temporary suspension
  * **Running** when the authorized User resumes Test Execution
  * **Completed** when the Test Run satisfies its defined completion condition

DIDO-TE records each transition and preserves the applicable Actor, time, reason, Governance Policies, and Evidence.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>