ENV-003f — Load Required Test Inputs

Go to ENV-003 — Establish Controlled Starting State

Before each Test Execution, the DIDO-TE SHALL load each Test Input specified by the applicable Test Definition into its designated Test Environment element.

• ENV-003 — Establish Controlled Starting State
• [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)

Loading each required Test Input establishes the data, values, events, messages, files, commands, or stimuli required by the applicable 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 Test Execution or undermining interpretation of the resulting Test Results.

• Test Environment
• Test Definition
• Test Execution
• Test Input
• Test Object
• Node
• Test Resource
• Configuration
• Evidence

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 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

• Add links to the architecture sections governing Test Input specification, loading, sequencing, integrity validation, Traceability, 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-003-establish-controlled-starting-state:env-003f-load-required-test-inputs#Statement&noheader&nofooter&noeditbtn}}