====== ENV-003f — Load Required Test Inputs ======
[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|Go to ENV-003 — Establish Controlled Starting State]]
===== Statement =====
Before each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]], the [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL load each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]] specified by the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] into its designated [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] element.
===== Derived From =====
* [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|ENV-003 — Establish Controlled Starting State]]
* [[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 =====
Loading each required [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]] establishes the data, values, events, messages, files, commands, or stimuli required by the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]].
Each loaded Test Input must correspond to its specified content, format, version, sequence, destination, and integrity information.
Controlled loading prevents a missing, incorrect, corrupted, obsolete, duplicated, or misdirected Test Input from changing the conditions of the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] or undermining interpretation of the resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
===== 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_execution|Test Execution]]
* [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]]
* [[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:c:configuration|Configuration]]
* [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
===== Verification =====
Verification confirms that:
* The applicable Test Definition identifies each required Test Input.
* The Test Definition specifies the content, format, version, sequence, destination, timing, and integrity information applicable to each Test Input.
* The DIDO-TE loads each required Test Input before Test Execution.
* Each loaded Test Input corresponds to its specified content, format, version, sequence, destination, timing, and integrity information.
* Each Test Input is available to its designated Test Environment element.
* The loaded Test Inputs exclude unspecified, obsolete, corrupted, duplicated, conflicting, and prohibited inputs.
* The DIDO-TE records the identity, version, integrity information, destination, and loading status of each Test Input.
* The DIDO-TE maintains [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among each Test Input, the applicable Test Definition, its designated Test Environment element, and the applicable Test Execution.
* A missing, incorrect, corrupted, obsolete, duplicated, misdirected, or untraceable Test Input constitutes nonconformance with this requirement.
Verification includes:
* Inspection of the Test Definition identifying each required Test Input
* Inspection of the specified Test Input content, format, version, sequence, destination, timing, and integrity information
* Observation of Test Input loading
* Comparison of each loaded Test Input with its specification
* Confirmation of Test Input availability to its designated Test Environment element
* Inspection for unspecified, obsolete, corrupted, duplicated, conflicting, and prohibited Test Inputs
* Inspection of Test Input identity, version, integrity, destination, and loading-status records
* Inspection of Traceability records connecting each Test Input to the Test Definition, designated Test Environment element, and Test Execution
* A negative assessment using a missing, incorrect, corrupted, obsolete, duplicated, misdirected, or untraceable Test Input
* Confirmation that the negative assessment produces a nonconformance result
===== Referenced By =====
{{backlinks>.}}
===== Related Architecture Sections =====
* Add links to the architecture sections governing Test Input specification, loading, sequencing, integrity validation, Traceability, and Test Execution admission.
===== 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-003-establish-controlled-starting-state:env-003f-load-required-test-inputs#Statement&noheader&nofooter&noeditbtn}}
----
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.