ENV-003d — Initialise Test Objects

Go to ENV-003 — Establish Controlled Starting State

Before each Test Execution, the DIDO-TE SHALL initialise each applicable Test Object to the state specified by the controlled descriptive information governing the Test Environment.

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

Initialising each applicable Test Object establishes the required state of the object subjected to examination during a Test Execution.

Test Object initialisation applies the required software, data, state, parameters, dependencies, interfaces, identity, and supporting resources specified by the controlled descriptive information.

A known initial state prevents an uninitialised, partially initialised, incorrectly initialised, or residual Test Object state from influencing the observed behaviour or resulting Test Results.

• Test Environment
• Test Definition
• Test Execution
• Test Object
• Baseline
• Configuration
• Test Resource
• Test Input

Verification confirms that:

• The controlled descriptive information identifies each Test Object applicable to the Test Execution.
• The controlled descriptive information specifies the required initial state of each applicable Test Object.
• The DIDO-TE initialises each applicable Test Object before Test Execution.
• Each Test Object reaches its specified initial state.
• Each Test Object contains the required software, data, parameters, dependencies, interfaces, identity, and supporting resources.
• The initialised state excludes residual Test Object state prohibited by the controlled descriptive information.
• The DIDO-TE records the identity, initialisation status, and resulting state of each Test Object.
• The DIDO-TE maintains Traceability among each Test Object, its specified initial state, its resulting state, and the applicable Test Execution.
• An absent, uninitialised, partially initialised, incorrectly initialised, residual, or untraceable Test Object state constitutes nonconformance with this requirement.

Verification includes:

• Inspection of the controlled descriptive information identifying each applicable Test Object
• Inspection of the specified initial state for each Test Object
• Observation of Test Object initialisation
• Comparison of each resulting Test Object state with its specified initial state
• Inspection of the applied software, data, parameters, dependencies, interfaces, identity, and supporting resources
• Inspection for prohibited residual Test Object state
• Inspection of Test Object identity, initialisation status, and resulting-state records
• Inspection of Traceability records connecting each Test Object to its specified state, resulting state, and Test Execution
• A negative assessment using an absent, uninitialised, partially initialised, incorrectly initialised, residual, or untraceable Test Object
• Confirmation that the negative assessment produces a nonconformance result

• Add links to the architecture sections governing Test Object lifecycle, Test Object initialisation, Test Object state, Configuration, residual-state control, 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-003d-initialise-test-objects#Statement&noheader&nofooter&noeditbtn}}