MO-002 — Reproducible Test Environments and Test Execution

Go to C.1 Mission Objectives

Original Requirement

The draft DIDO-TE source material states:

Create repeatable testing scenarios, including regression testing, that allow rigorous evaluation of distributed systems under different conditions and configurations.

Assessment of Original Requirement

The Original Requirement preserves the approved mission-level intent that DIDO-TE provide repeatable or reproducible testing under different conditions and Configurations.

The Original Requirement does not express an independently interpretable or independently verifiable normative obligation.

The following Specification Discipline and Authoring findings apply:

Create does not identify an explicit responsible ActorCreate does not use an explicit normative modalRepeatable does not identify the required degree or method of ReproducibilityTesting scenarios does not use defined terms such as Test Definition, Test Sequence, Test Environment, or Test ExecutionIncluding regression testing provides an example but does not establish a bounded scopeAllow is a weak verb that does not identify an observable DIDO-TE behaviorRigorous evaluation is subjective and does not identify measurable evaluation criteriaDistributed systems does not identify the selected Distributed System, Test Items, Nodes, or Node Sets subject to testingDifferent conditions does not identify the controlled conditions, variable conditions, or permitted differencesDifferent configurations does not identify the Configurations that DIDO-TE must preserve, recreate, or varyThe Original Requirement does not identify the applicable Acceptance CriteriaThe Original Requirement does not identify the Evidence required to demonstrate ReproducibilityThe source uses the word repeatable, while the proposed canonical requirements use reproducible and Reproducibility. The requirement owner must confirm whether:

Repeatability and Reproducibility express the same approved intent in this contextRepeatability identifies a narrower controlled-condition obligationReproducibility identifies a broader obligation that permits defined changes to operators, resources, locations, or other conditionsSeparate requirements for Repeatability and Reproducibility are necessaryThe Original Requirement combines at least two independently verifiable outcomes:

Recreating a selected Test Environment within an established permitted variationRepeating selected Test Execution within an established permitted variationThese outcomes require separate verification.

A Test Environment can be recreated successfully even when repeated Test Execution produces unacceptable differences in the resulting Test Results.

Test Execution can also produce acceptable Test Results even when DIDO-TE has not demonstrated that the Test Environment was recreated according to its controlling Configuration.

The Original Requirement therefore requires:

Identification of DIDO-TE as the responsible ActorReplacement of nonnormative language with explicit normative obligationsSelection of Repeatability, Reproducibility, or both as the controlling qualityDefinition of the Test Environment characteristics subject to reproductionDefinition of the Test Execution information subject to reproductionSeparation of Test Environment Reproducibility from Test Execution ReproducibilityIdentification of the permitted variation for each outcomeIdentification of the applicable Acceptance CriteriaIdentification of the Evidence required to verify each outcomeConfirmation that the derived requirements collectively preserve the complete intent of MO-002The decomposition preserves MO-002 as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

Proposed Statements

The Original Requirement is decomposed into the following proposed replacement requirements:

Requirement Status

Issues

The following unresolved issues affect the decomposition of MO-002:

Notes for Editors

This page should retain the stable parent requirement identifier MO-002.

This page is a non-leaf requirement page and retains a trailing :start in its namespace.

The child requirements are leaf requirement pages and omit a trailing :start from their namespaces.

This page preserves:

The Original RequirementThe assessment of the Original RequirementThe reason for decompositionTraceability to the proposed replacement requirementsThe unresolved cross-cutting issues affecting the decompositionThe supersession decisionMO-002a addresses the Reproducibility of a selected Test Environment.

MO-002b addresses the Reproducibility of selected Test Execution.

The child requirements must not combine Test Environment recreation and Test Execution repetition into a single normative Statement.

The child requirements should identify independently verifiable Acceptance Criteria for:

The selected Test EnvironmentThe selected Test ExecutionThe controlling ConfigurationsThe controlling VersionsThe applicable Test Argument ValuesThe Starting ConditionsThe Timing ConditionsThe permitted Execution PathsThe permitted variationThe comparison methodThe treatment of nondeterministic behaviorThe required EvidenceThe required ProvenanceThe required TraceabilityMO-002 should not be marked as superseded until the requirement owner:

Confirms the authoritative Original Requirement and its controlling citationApproves the interpretation of Repeatability and ReproducibilityApproves MO-002aApproves MO-002bConfirms that the child requirements collectively preserve the complete approved intent of MO-002Confirms that no additional child requirements are requiredAfter supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.

Material changes to the decomposition should update the child requirements, Requirement Status, Issues, source records, and Traceability records.

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.