dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-002-configure-test-environment:env-002l-validate-test-environment-configuration

This is an old revision of the document!


ENV-002l — Validate Test Environment Configuration

The DIDO-TE SHALL validate the resulting Test Environment Configuration against its controlled descriptive information before Test Execution.

Validating the resulting Test Environment Configuration determines whether the instantiated and provisioned environment conforms to its controlled descriptive information.

Validation compares the actual Test Objects, Nodes, Test Resources, Configuration values, communication relationships, constraints, Deployment Targets, versions, Baselines, and supporting services with their specified states.

Completing validation before Test Execution prevents an invalid or uncontrolled Test Environment Configuration from affecting execution or undermining interpretation of the resulting Test Results.

Verification confirms that:

  • The DIDO-TE validates the resulting Test Environment Configuration before Test Execution.
  • Validation compares the resulting Configuration with the applicable controlled descriptive information.
  • Validation assesses the completeness and correctness of the instantiated Test Objects and Nodes.
  • Validation assesses the completeness, correctness, and availability of the provisioned Test Resources.
  • Validation assesses the applied Configuration values.
  • Validation assesses the established and prohibited communication relationships.
  • Validation assesses compliance with the applicable environmental, security, and deployment Constraints.
  • Validation assesses the applicable Deployment Targets, versions, and Baselines.
  • Validation produces a determinate conformance result.
  • The DIDO-TE records the validation method, observations, findings, result, and applicable Configuration as Evidence.
  • The DIDO-TE maintains Traceability among the controlled descriptive information, resulting Configuration, validation Evidence, and applicable Test Execution.
  • The DIDO-TE prevents Test Execution when validation identifies an unresolved nonconformance.
  • Missing, incomplete, unsuccessful, or untraceable validation constitutes nonconformance with this requirement.

Verification includes:

  • Inspection of the controlled descriptive information governing the Test Environment
  • Inspection of the resulting Test Environment Configuration
  • Inspection of the validation method, observations, findings, result, and Evidence
  • Comparison of the validated Configuration with the instantiated and provisioned Test Environment
  • Inspection of Traceability records connecting the controlled information, Configuration, validation Evidence, and applicable Test Execution
  • A negative assessment using a Test Environment Configuration containing a known nonconformance
  • Confirmation that validation identifies the nonconformance
  • Confirmation that the DIDO-TE prevents Test Execution while the nonconformance remains unresolved
  • Add links to the architecture sections governing Test Environment validation, Configuration conformance, Evidence, exception handling, and Test Execution admission.

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-002l-validate-test-environment-configuration#Statement&noheader&nofooter&noeditbtn}}

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

  • dido/03-dido-te/99-annexes/annex-c-requirements/03-functional-requirements/03-01-test-environment-requirements/env-002-configure-test-environment/env-002l-validate-test-environment-configuration.1787081664.txt.gz
  • Last modified: 2026/08/18 12:34
  • by nick_dido