====== ENV-002 — Configure Test Environment ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:start|Go to C.3.1 Test Environment Requirements]]

ENV-002 is a non-leaf requirement group governing the controlled configuration of each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] before [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].

Conformance is assessed against the individual leaf requirements listed below. ENV-002 does not establish a separate conformance obligation.

===== Contents =====

{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-002-configure-test-environment#1|js navbar nocookie maxjs#1 id#dido_te_env_002_requirements_nav}}

===== Source =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-006|[DTE6] Structured Information Processing Reference Architecture (SIP-RA)]]
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-007|[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)]]

===== Rationale =====

A controlled [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] establishes the operating state of a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] before [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].

Configuring the Test Environment according to its controlled descriptive information establishes consistency between the defined environment and its instantiated state.

Recording the resulting Configuration preserves the information required to reproduce the Test Environment, compare separate Test Executions, identify environmental differences, and interpret the resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].

Validation before Test Execution prevents a Test Execution performed in an incorrectly configured Test Environment from being represented as originating from the specified Test Environment and [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].

The leaf requirements in this group define the individually verifiable obligations governing Test Environment Configuration and its validation.

===== Applies To =====

  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Object]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

===== Traceability =====

{{backlinks>.}}

===== ConOps Relationship =====

Add links to the ConOps activities and architecture sections governing Test Environment configuration, provisioning, validation, and Baseline control.

===== Delivery Phase =====

Assign the applicable delivery phase.

===== Requirement Status =====

Draft

===== Notes for Editors =====

The subordinate leaf requirements ENV-002a through ENV-002l define the normative obligations and corresponding verification criteria for ENV-002.

We removed the former ENV-002 Statement and Verification sections because ENV-002 is a non-leaf requirement group and does not establish an independently verifiable conformance obligation.

After you create and finalize all subordinate requirement pages, you may remove explicit child links because the ''indexmenu'' automatically discovers the leaf pages.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>