MO-003 — Automated Test Execution

Go to C.1 Mission Objectives

Statement

DIDO-TE SHALL complete a selected 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 scenariosAutomated performance of Test SequencesCoordinated performance of testing activities across NodesDelivery of recorded inputs to NodesCollection of outputs from NodesAutomated generation of Test ResultsPreservation of supporting Evidence

MO-003 expresses the common mission-level outcome. Detailed obligations addressing Test Execution initiation, sequencing, scheduling, coordination, monitoring, Exception Handling, termination, Test Result generation, and Evidence preservation remain separate Operational, Functional, Logging and Auditing, Reliability, Performance, and Data Management Requirements.

Rationale

Automated Test Execution permits organizations to perform complex and repeated testing consistently without requiring a human Actor to perform each Test Step.

Automation supports:

Consistent performance of Test DefinitionsCoordinated performance of Test SequencesPerformance of Test Steps in the defined orderApplication of Test Argument ValuesEvaluation of applicable Starting ConditionsEvaluation of applicable Timing ConditionsSelection of permitted Execution PathsEnforcement of applicable TimeoutsDetection of Test Execution ExceptionsPerformance of applicable Exception HandlingCoordination among Nodes and Node SetsCollection of observations and measurementsGeneration of Test ResultsPreservation of EvidenceRepetition of testing for regression analysisPerformance of testing in connected, disconnected, and air-gapped environmentsThe 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 Test DefinitionSelecting a Test EnvironmentSupplying or approving Test Argument ValuesEstablishing Acceptance CriteriaAuthorizing Test ExecutionInitiating a Test RunMonitoring Test ExecutionRequesting cancellationReviewing Test ResultsMaking a Validation DecisionAfter initiation, DIDO-TE performs the selected Test Execution without requiring a human Actor to:

Perform a Test StepSelect an Execution PathTransfer an intermediate resultAdvance the Test SequenceDetect a Test Execution ExceptionPerform automated Exception HandlingDetermine whether the Test Run satisfied its completion conditionAssign the applicable Test Run StateAn 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 Test Run Termination Reason.

A Test Run that enters the Terminated Test Run State without satisfying its defined completion condition is an Incomplete Test Run.

The detailed requirements establish:

The event constituting initiationThe event constituting completionThe permitted pre-execution human activitiesThe permitted human control operations after initiationThe applicable Test DefinitionThe applicable Test EnvironmentThe automated Test StepsThe required Test ExecutablesThe required Execution FacilitiesThe Test Execution Exceptions subject to detectionThe applicable Exception HandlingThe applicable Test Run StatesThe permitted Test Run State transitionsThe applicable Test Run Termination ReasonsThe treatment of Incomplete Test RunsThe required Test Results and Evidence

Applies To

This requirement applies to:

Selected Test ExecutionAutomated Test ExecutionAcceptance CriteriaActorsHuman ActorsUsersTest DefinitionsTest SequencesSequence StepsTest StepsTest ExecutablesExecutable InstructionsExecutable ArtifactsExecution FacilitiesTest ArgumentsTest Argument ValuesStarting ConditionsTiming ConditionsExecution PathsTimeoutsTest Execution ExceptionsException HandlingTest EnvironmentsNodesNode SetsTest RunsTest Run StatesTest Run Termination ReasonsIncomplete Test RunsTest ResultsConnected EnvironmentsDisconnected EnvironmentsAir-Gapped EnvironmentsEvidenceProvenanceTraceability

Verification

Verification confirms that:

The selected Test Execution is identifiedThe applicable Test Definition and Version are identifiedThe selected Test Environment is identifiedThe Acceptance Criteria identify the event constituting Test Execution initiationThe Acceptance Criteria identify the event constituting Test Execution completionThe Acceptance Criteria identify the human activities permitted before initiationThe Acceptance Criteria identify the human control operations permitted after initiationThe Acceptance Criteria identify the Test Steps subject to automated performanceThe Acceptance Criteria identify the applicable Test ExecutablesThe Acceptance Criteria identify the applicable Execution FacilitiesThe Acceptance Criteria identify the applicable Test Argument ValuesThe Acceptance Criteria identify the applicable Starting ConditionsThe Acceptance Criteria identify the applicable Timing ConditionsThe Acceptance Criteria identify the permitted Execution PathsThe Acceptance Criteria identify the applicable TimeoutsThe Acceptance Criteria identify the Test Execution Exceptions subject to detectionThe Acceptance Criteria identify the applicable Exception HandlingThe Acceptance Criteria identify any Exception Handling requiring human interventionThe Acceptance Criteria identify the applicable Test Run StatesThe Acceptance Criteria identify the permitted transitions between Test Run StatesThe Acceptance Criteria identify the applicable Test Run Termination ReasonsThe Acceptance Criteria identify the treatment of Incomplete Test Runs for each applicable Test Run Termination ReasonAn authorized Actor initiates the selected Test ExecutionDIDO-TE performs each automated Test Step after initiationDIDO-TE advances the applicable Test Sequence without requiring human interventionDIDO-TE transfers required intermediate information without requiring human interventionDIDO-TE evaluates applicable progression conditions without requiring human interventionDIDO-TE selects only permitted Execution PathsDIDO-TE applies the applicable TimeoutsDIDO-TE detects the Test Execution Exceptions identified by the Acceptance CriteriaDIDO-TE performs the applicable Exception Handling for each detected Test Execution ExceptionDIDO-TE performs automated Exception Handling without requiring human interventionDIDO-TE records each detected Test Execution ExceptionDIDO-TE records the Exception Handling performed for each detected Test Execution ExceptionDIDO-TE records each applicable Test Run StateDIDO-TE records each transition between Test Run StatesDIDO-TE assigns the Completed Test Run State when the Test Run satisfies its defined completion conditionDIDO-TE assigns the Terminated Test Run State when the Test Run stops without satisfying its defined completion conditionDIDO-TE records the applicable Test Run Termination Reason when the Test Run enters the Terminated Test Run StateDIDO-TE identifies a Test Run that enters the Terminated Test Run State without satisfying its defined completion condition as an Incomplete Test RunDIDO-TE reaches the state identified as Test Execution completion without requiring human interventionDIDO-TE records any human control operation performed after initiationDIDO-TE produces the required Test ResultsThe verification record preserves 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 Evidence

Referenced By

The following pages reference this requirement:

Delivery Phase

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

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:

as the responsible ActorA selected Test Execution as the automated activityTest Execution initiation as the beginning of the automation boundaryTest Execution completion as the required outcomeAbsence of required human intervention between initiation and completion as the automation constraintThe supporting requirements should define:

Test Execution selectionTest Definition selectionTest Environment selectionTest Execution initiationTest Execution completionTest Run StatesTest Run State transitionsTest Run Termination ReasonsIncomplete Test RunsPre-execution human activitiesPermitted human control operationsAutomated Test StepsTest ExecutablesExecution FacilitiesTest Argument ValuesStarting ConditionsTiming ConditionsExecution PathsTimeoutsTest Execution Exception detectionException HandlingRetry behaviorPause behaviorCancellation behaviorTermination behaviorCompensation behaviorRecovery behaviorTest Result generationEvidence generationProvenanceTraceabilityA 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 Test Run State can produce a Test Result assigned a failing Verdict. A failing Verdict does not by itself make the Test Run an Incomplete Test Run.

A Test Run that enters the Terminated Test Run State has an applicable Test Run Termination Reason and is an Incomplete Test Run when it did not satisfy its defined completion condition.

A detected Test Execution Exception does not necessarily prevent DIDO-TE from satisfying MO-003. DIDO-TE can satisfy MO-003 when automated 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:

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

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

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.