====== Starting Condition ======

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

===== Discussion =====

A Starting Condition is a state, value, event, or circumstance established or observed at the start of an activity.

A Starting Condition can apply to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_sequence|Test Sequence]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:s:sequence_step|Sequence Step]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]]
  * A process
  * An operation
  * Another activity with an identifiable starting event

A Starting Condition can identify:

  * The applicable activity
  * The starting event
  * The starting time
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * The applicable Test Environment Version
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_item|Test Items]]
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]]
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Set]]
  * The applicable states
  * The applicable values
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]]
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]]
  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resources]]
  * The applicable dependencies
  * The applicable external conditions
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Definition =====

//state, value, event, or circumstance established or observed at the start of an activity//

===== Source =====

Adapted from:

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

OMG TestIF supports Test Run starting times, starting Sequenced Test Objects, Test Argument Values, Test Environments, and occurrence-specific Sequence Step information.

OMG TestIF does not define Starting Condition as a separate TestIF model element. This definition introduces the term to identify the state and circumstances that apply when an activity begins.

===== Note =====

Use the singular glossary term Starting Condition. Link plural usage to the same controlling page:

<code dokuwiki>
[[dido:99_annexes:annex-b-terms-and-definitions:s:starting_condition|Starting Conditions]]
</code>

A Starting Condition differs from a condition that must be satisfied before an activity begins:

  * The prior condition determines whether the activity can begin
  * The Starting Condition identifies the state, value, event, or circumstance that applies when the activity begins

The same information can perform both roles when the activity requires a particular state at its starting event.

A Starting Condition differs from an [[dido:99_annexes:annex-b-terms-and-definitions:e:expected_result|Expected Result]]:

  * A Starting Condition identifies the applicable state at the start of an activity
  * An Expected Result identifies the anticipated outcome used to evaluate a Test Result

A Starting Condition differs from a [[dido:99_annexes:annex-b-terms-and-definitions:t:timing_condition|Timing Condition]]:

  * A Starting Condition identifies the state or circumstance applicable at the start
  * A Timing Condition constrains or characterizes when an event or activity starts, occurs, completes, repeats, or relates temporally to another event or activity

A Starting Condition must identify the applicable subject and activity. A value such as ''ACTIVE'' does not establish a complete Starting Condition unless the definition identifies what must have that value and when it applies.

Reproducible Test Execution can require preservation or recreation of applicable Starting Conditions.

The applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] determine:

  * Which Starting Conditions require exact reproduction
  * Which Starting Conditions permit variation
  * The permitted variation
  * The observation or measurement method
  * The Evidence required to demonstrate the Starting Conditions

===== Example =====

A Test Run evaluates a Node Set beginning from an approved distributed state.

The Starting Conditions identify:

  * Test Environment Version ''3.2''
  * Configuration Version ''7.1''
  * Node Set ''NS-004''
  * The Version of each Node
  * The state of each Node
  * The approved Baseline
  * The applicable Test Argument Values
  * The available Operational Resources
  * The starting network Configuration
  * The starting event
  * The starting time

The Test Run records the observed Starting Conditions before Test Execution proceeds.

A repeated Test Run uses the recorded Starting Conditions to recreate the required starting state and preserve Reproducibility.

----

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