ENV-002k — Record Test Environment Configuration

Go to ENV-002 — Configure Test Environment

The DIDO-TE SHALL record the resulting Test Environment Configuration before Test Execution.

• [DTE5] DIDO-TE Requirements Register, source requirement identifier and obligation to be assigned
• [DTE6] Structured Information Processing Reference Architecture (SIP-RA)
• [DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

Recording the resulting Test Environment Configuration preserves the controlled state established through instantiation, provisioning, configuration, communication, constraint enforcement, and application of version and Baseline information.

The record identifies the actual Test Objects, Nodes, Test Resources, Configuration values, communication relationships, Deployment Targets, versions, Baselines, constraints, and supporting services present before Test Execution.

This record provides Evidence of the Test Environment state and supports Traceability, Reproducibility, configuration comparison, and interpretation of the resulting Test Results.

• Test Environment
• Configuration
• Baseline
• Test Object
• Node
• Test Resource
• Deployment Target
• Evidence
• Test Execution

Verification confirms that:

• The DIDO-TE records the resulting Test Environment Configuration before Test Execution.
• The record identifies each instantiated Test Object and Node.
• The record identifies each provisioned Test Resource.
• The record contains the applied Configuration values.
• The record identifies the established communication relationships.
• The record identifies the applicable environmental, security, and deployment Constraints and their enforcement states.
• The record identifies the applicable Deployment Targets.
• The record contains the applied version and Baseline information.
• The record identifies the time at which the Configuration was captured and the Test Execution to which it applies.
• The DIDO-TE protects the Configuration record against undetected modification.
• The DIDO-TE maintains Traceability among the controlled Test Environment information, the resulting Configuration, and the applicable Test Execution.
• A missing, incomplete, inaccurate, altered, or untraceable Configuration record constitutes nonconformance with this requirement.

Verification includes:

• Inspection of the resulting Test Environment Configuration record
• Comparison of the record with the instantiated and provisioned Test Environment
• Inspection of recorded Configuration values, communication relationships, Constraints, Deployment Targets, versions, and Baselines
• Inspection of the Configuration record’s capture time and applicable Test Execution identifier
• Inspection of integrity protections applied to the Configuration record
• Inspection of Traceability records connecting the controlled information, resulting Configuration, and applicable Test Execution
• A negative assessment using a missing, incomplete, inaccurate, altered, or untraceable Configuration record
• Confirmation that the negative assessment produces a nonconformance result

• Add links to the architecture sections governing Test Environment Configuration, configuration recording, Evidence, integrity protection, and Traceability.

Assign the applicable delivery phase.

Draft

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-002-configure-test-environment:env-002k-record-test-environment-configuration#Statement&noheader&nofooter&noeditbtn}}