ENV-004b — Control Baselines and Configurations
Statement
For each Test Execution, the DIDO-TE SHALL apply and maintain the Baselines and Configuration values specified by the applicable Test Definition.
Derived From
-
[DTE5] DIDO-TE Requirements Register, source requirement identifier and obligation to be assigned
Rationale
Baselines and Configuration values determine the composition and operating state of the Test Environment, participating Nodes, Test Objects, and supporting Test Resources.
Uncontrolled changes to software versions, machine images, container images, dependencies, parameters, security settings, interfaces, or infrastructure characteristics introduce environmental variation into a Test Execution.
Applying the required Baselines and Configuration values before execution, maintaining them during execution, and detecting unauthorised changes preserve the conditions needed to interpret and compare Test Results.
A required change during Test Execution forms part of the Test Definition and receives explicit control and recording. An unintended or unauthorised change constitutes environmental variation.
Applies To
Verification
Verification confirms that:
-
The applicable Test Definition identifies each required Baseline and Configuration value.
-
Each required Baseline and Configuration value has a unique identity and controlled version.
-
The DIDO-TE applies each required Baseline and Configuration value before Test Execution.
-
The applied Baselines and Configuration values correspond to the controlled descriptive information.
-
The DIDO-TE maintains the required Baselines and Configuration values throughout the period specified by the Test Definition.
-
The DIDO-TE detects an unintended or unauthorised change to an applied Baseline or Configuration value.
-
A change required by the Test Definition occurs at the specified event, sequence position, or time.
-
The DIDO-TE records the applied Baselines, Configuration values, authorised changes, detected deviations, and resulting states as Evidence.
-
The DIDO-TE maintains Traceability among each Baseline and Configuration value, its controlled source, affected Test Environment element, Test Definition, Test Execution, and Test Results.
-
A missing, incorrect, uncontrolled, altered, unsupported, or untraceable Baseline or Configuration value constitutes nonconformance with this requirement.
Verification includes:
-
Inspection of the Baselines and Configuration values specified by the Test Definition
-
Inspection of Baseline and Configuration identities and versions
-
Comparison of the required and applied Baselines and Configuration values
-
Observation of Baseline and Configuration control during Test Execution
-
Observation of a change required by the Test Definition
-
Testing with an unintended or unauthorised Baseline or Configuration change
-
Confirmation that the DIDO-TE detects and records the change
-
Inspection of Baseline, Configuration, change, deviation, and resulting-state Evidence
-
Inspection of Traceability records connecting each Baseline and Configuration value to its source, affected element, Test Definition, Test Execution, and Test Results
-
Confirmation that an incorrect, uncontrolled, or untraceable Baseline or Configuration produces a nonconformance result
Referenced By
Related Architecture Sections
-
Add links to the architecture sections governing Baseline management, Configuration management, change control, environmental monitoring, Evidence, and Traceability.
Delivery Phase
Assign the applicable delivery phase.
Requirement Status
Draft
Statement Reference
Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:
{{section>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-004-provide-deterministic-test-environment:env-004b-control-baselines-and-configurations#Statement&noheader&nofooter&noeditbtn}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.