MO-003 — Automated Test Execution [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.
====== MO-003 — Automated Test Execution ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to C.1 Mission Objectives]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL complete a selected [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] without human intervention after initiation.

===== Source =====

This requirement consolidates mission-level intent from the DIDO-TE source material addressing:

  * Automated execution of testing scenarios
  * Automated performance of [[dido:99_annexes:annex-b-terms-and-definitions:t:test_sequence|Test Sequences]]
  * Coordinated performance of testing activities across [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]]
  * Delivery of recorded inputs to Nodes
  * Collection of outputs from Nodes
  * Automated generation of [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]
  * Preservation of supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

<todo>Identify the authoritative source requirements, original requirement identifiers, and controlling citations for the automated Test Execution objective.</todo>

MO-003 expresses the common mission-level outcome. Detailed obligations addressing Test Execution initiation, sequencing, scheduling, coordination, monitoring, [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]], termination, Test Result generation, and Evidence preservation remain separate Operational, Functional, Logging and Auditing, Reliability, Performance, and Data Management [[dido:99_annexes:annex-b-terms-and-definitions:r:requirement|Requirements]].

===== Rationale =====

Automated [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] permits organizations to perform complex and repeated testing consistently without requiring a human [[dido:99_annexes:annex-b-terms-and-definitions:a:actor|Actor]] to perform each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]].

Automation supports:

  * Consistent performance of [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definitions]]
  * Coordinated performance of [[dido:99_annexes:annex-b-terms-and-definitions:t:test_sequence|Test Sequences]]
  * Performance of Test Steps in the defined order
  * Application of [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]]
  * Evaluation of applicable [[dido:99_annexes:annex-b-terms-and-definitions:s:starting_condition|Starting Conditions]]
  * Evaluation of applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:timing_condition|Timing Conditions]]
  * Selection of permitted [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_path|Execution Paths]]
  * Enforcement of applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:timeout|Timeouts]]
  * Detection of [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exceptions]]
  * Performance of applicable [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]]
  * Coordination among [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] and [[dido:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Sets]]
  * Collection of observations and measurements
  * Generation of [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]
  * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * Repetition of testing for regression analysis
  * Performance of testing in connected, disconnected, and air-gapped environments

The phrase **without human intervention after initiation** establishes the automation boundary for MO-003.

MO-003 does not prohibit a human Actor from:

  * Creating or selecting a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
  * Selecting a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * Supplying or approving Test Argument Values
  * Establishing [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]
  * Authorizing Test Execution
  * Initiating a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]]
  * Monitoring Test Execution
  * Requesting cancellation
  * Reviewing Test Results
  * Making a [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_decision|Validation Decision]]

After initiation, DIDO-TE performs the selected Test Execution without requiring a human Actor to:

  * Perform a Test Step
  * Select an Execution Path
  * Transfer an intermediate result
  * Advance the Test Sequence
  * Detect a Test Execution Exception
  * Perform automated Exception Handling
  * Determine whether the Test Run satisfied its completion condition
  * Assign the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_state|Test Run State]]

An authorized human request to pause, cancel, or otherwise control a Test Run does not by itself demonstrate a failure of automated Test Execution when the applicable Acceptance Criteria permit the requested operation.

A human notification does not by itself constitute human intervention. A human response affecting the progression of Test Execution constitutes human intervention.

Exception Handling requiring an Actor to select a response, authorize continued Test Execution, supply information, or perform an operation does not satisfy the automation constraint during the period in which DIDO-TE requires the Actor’s response.

A detected Test Execution Exception does not necessarily prevent completion of automated Test Execution. Automated Exception Handling can resolve the Test Execution Exception and permit the Test Run to continue.

When Exception Handling does not resolve the Test Execution Exception, DIDO-TE can place the Test Run in the Terminated Test Run State and record the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_termination_reason|Test Run Termination Reason]].

A Test Run that enters the Terminated Test Run State without satisfying its defined completion condition is an [[dido:99_annexes:annex-b-terms-and-definitions:i:incomplete_test_run|Incomplete Test Run]].

The detailed requirements establish:

  * The event constituting initiation
  * The event constituting completion
  * The permitted pre-execution human activities
  * The permitted human control operations after initiation
  * The applicable Test Definition
  * The applicable Test Environment
  * The automated Test Steps
  * The required [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executables]]
  * The required [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facilities]]
  * The Test Execution Exceptions subject to detection
  * The applicable Exception Handling
  * The applicable Test Run States
  * The permitted Test Run State transitions
  * The applicable Test Run Termination Reasons
  * The treatment of Incomplete Test Runs
  * The required Test Results and Evidence

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
  * Selected [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
  * Automated Test Execution
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:actor|Actors]]
  * Human Actors
  * [[dido:99_annexes:annex-b-terms-and-definitions:u:user|Users]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definitions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_sequence|Test Sequences]]
  * [[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]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executables]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_instruction|Executable Instructions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifacts]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facilities]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument|Test Arguments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:s:starting_condition|Starting Conditions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:timing_condition|Timing Conditions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_path|Execution Paths]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:timeout|Timeouts]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exceptions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Sets]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Runs]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_state|Test Run States]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_termination_reason|Test Run Termination Reasons]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:incomplete_test_run|Incomplete Test Runs]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Verification =====

Verification confirms that:

  - The selected [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] is identified
  - The applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] and [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Version]] are identified
  - The selected [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] is identified
  - The [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] identify the event constituting Test Execution initiation
  - The Acceptance Criteria identify the event constituting Test Execution completion
  - The Acceptance Criteria identify the human activities permitted before initiation
  - The Acceptance Criteria identify the human control operations permitted after initiation
  - The Acceptance Criteria identify the Test Steps subject to automated performance
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executables]]
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facilities]]
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]]
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:s:starting_condition|Starting Conditions]]
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:timing_condition|Timing Conditions]]
  - The Acceptance Criteria identify the permitted [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_path|Execution Paths]]
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:timeout|Timeouts]]
  - The Acceptance Criteria identify the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exceptions]] subject to detection
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]]
  - The Acceptance Criteria identify any Exception Handling requiring human intervention
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_state|Test Run States]]
  - The Acceptance Criteria identify the permitted transitions between Test Run States
  - The Acceptance Criteria identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_termination_reason|Test Run Termination Reasons]]
  - The Acceptance Criteria identify the treatment of [[dido:99_annexes:annex-b-terms-and-definitions:i:incomplete_test_run|Incomplete Test Runs]] for each applicable Test Run Termination Reason
  - An authorized Actor initiates the selected Test Execution
  - DIDO-TE performs each automated Test Step after initiation
  - DIDO-TE advances the applicable Test Sequence without requiring human intervention
  - DIDO-TE transfers required intermediate information without requiring human intervention
  - DIDO-TE evaluates applicable progression conditions without requiring human intervention
  - DIDO-TE selects only permitted Execution Paths
  - DIDO-TE applies the applicable Timeouts
  - DIDO-TE detects the Test Execution Exceptions identified by the Acceptance Criteria
  - DIDO-TE performs the applicable Exception Handling for each detected Test Execution Exception
  - DIDO-TE performs automated Exception Handling without requiring human intervention
  - DIDO-TE records each detected Test Execution Exception
  - DIDO-TE records the Exception Handling performed for each detected Test Execution Exception
  - DIDO-TE records each applicable Test Run State
  - DIDO-TE records each transition between Test Run States
  - DIDO-TE assigns the Completed Test Run State when the Test Run satisfies its defined completion condition
  - DIDO-TE assigns the Terminated Test Run State when the Test Run stops without satisfying its defined completion condition
  - DIDO-TE records the applicable Test Run Termination Reason when the Test Run enters the Terminated Test Run State
  - DIDO-TE identifies a Test Run that enters the Terminated Test Run State without satisfying its defined completion condition as an Incomplete Test Run
  - DIDO-TE reaches the state identified as Test Execution completion without requiring human intervention
  - DIDO-TE records any human control operation performed after initiation
  - DIDO-TE produces the required [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]
  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Acceptance Criteria, Test Definition, Test Environment, Test Execution, Test Run, Test Run State transitions, detected Test Execution Exceptions, performed Exception Handling, applicable Test Run Termination Reason, Incomplete Test Run classification, performed Test Steps, Execution Path, Test Results, human control operations, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:03-dido-te}}

===== Delivery Phase =====

<todo>TBD</todo>

===== Implementation Status =====

<todo>Assess the current DIDO-TE implementation against the automated Test Execution obligation established by MO-003.</todo>

===== Requirement Status =====

<todo>Review and accept MO-003 as a proposed Mission Objective consolidated from the automated Test Execution intent in the DIDO-TE source material.</todo>

----
===== Issues =====

The following unresolved issues affect this requirement:

<todo>Identify the authoritative source requirements, original requirement identifiers, and controlling citations for automated Test Execution.</todo>

<todo>Define the event constituting initiation of automated Test Execution.</todo>

<todo>Define the event constituting completion of automated Test Execution.</todo>

<todo>Define the human activities permitted before Test Execution initiation.</todo>

<todo>Define the human control operations permitted after Test Execution initiation.</todo>

<todo>Define whether every Test Step in the selected Test Execution must be automated.</todo>

<todo>Define the required behavior when the selected Test Definition contains a Test Step requiring human performance.</todo>

<todo>Define the required behavior when an applicable Test Executable or Execution Facility is unavailable.</todo>

<todo>Identify the Test Execution Exceptions DIDO-TE must detect during automated Test Execution.</todo>

<todo>Define the Exception Handling applicable to each Test Execution Exception.</todo>

<todo>Define the retry, pause, cancellation, termination, compensation, and recovery operations permitted during automated Exception Handling.</todo>

<todo>Define which Exception Handling operations can require human intervention.</todo>

<todo>Define the treatment of Incomplete Test Runs for each applicable Test Run Termination Reason.</todo>

<todo>Define the Test Results and Evidence DIDO-TE must produce during automated Test Execution.</todo>

----
===== Notes for Editors =====

This requirement page should retain the stable requirement identifier ''MO-003''.

This page is a leaf requirement page and omits a trailing '':start'' from its namespace.

MO-003 consolidates mission-level intent from multiple source statements. MO-003 does not result from splitting a single parent requirement and therefore uses a **Source** section rather than a **Derived From** section.

Changes to the Statement should preserve:

  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] as the responsible Actor
  * A selected [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] as the automated activity
  * Test Execution initiation as the beginning of the automation boundary
  * Test Execution completion as the required outcome
  * Absence of required human intervention between initiation and completion as the automation constraint

The supporting requirements should define:

  * Test Execution selection
  * Test Definition selection
  * Test Environment selection
  * Test Execution initiation
  * Test Execution completion
  * Test Run States
  * Test Run State transitions
  * Test Run Termination Reasons
  * Incomplete Test Runs
  * Pre-execution human activities
  * Permitted human control operations
  * Automated Test Steps
  * Test Executables
  * Execution Facilities
  * Test Argument Values
  * Starting Conditions
  * Timing Conditions
  * Execution Paths
  * Timeouts
  * Test Execution Exception detection
  * Exception Handling
  * Retry behavior
  * Pause behavior
  * Cancellation behavior
  * Termination behavior
  * Compensation behavior
  * Recovery behavior
  * Test Result generation
  * Evidence generation
  * Provenance
  * Traceability

A permitted human request to pause, cancel, or otherwise control an automated Test Run should not constitute a failure of MO-003 when the Acceptance Criteria authorize the operation.

A Test Definition containing a Test Step requiring human performance cannot satisfy MO-003 unless the Acceptance Criteria exclude the Test Step from the selected automated Test Execution or an automated Test Executable implements the Test Step.

A Test Run that enters the Completed [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_state|Test Run State]] can produce a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]] assigned a failing [[dido:99_annexes:annex-b-terms-and-definitions:v:verdict|Verdict]]. A failing Verdict does not by itself make the Test Run an [[dido:99_annexes:annex-b-terms-and-definitions:i:incomplete_test_run|Incomplete Test Run]].

A Test Run that enters the Terminated Test Run State has an applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run_termination_reason|Test Run Termination Reason]] and is an Incomplete Test Run when it did not satisfy its defined completion condition.

A detected [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exception]] does not necessarily prevent DIDO-TE from satisfying MO-003. DIDO-TE can satisfy MO-003 when automated [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]] resolves the Test Execution Exception and Test Execution reaches its defined completion state without human intervention.

Exception Handling requiring an Actor to select a response, authorize continuation, supply information, or perform an operation constitutes human intervention for MO-003.

Material changes should receive review and should update the verification criteria, source records, supporting requirements, and Issues section.

To reference this requirement Statement from another Wiki page, insert:

<code dokuwiki>
{{section>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-003#Statement&noheader&nofooter&noeditbtn}}
</code>

Do not rename this page after an external citation unless a redirect or move plan is in place.

----

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