Objective
Ensure the COTS test environment remains isolated and the test design remains structured.
Control Activity
Before test execution, Technology verifies that the test environment is isolated, access-controlled, intake-tested and sufficiently representative of production. Test cases must be traceable to acceptance criteria and cover expected, unexpected and invalid inputs using structured design techniques.
Evidence
- Expected evidence: environment intake record
- Expected evidence: test case set
- Expected evidence: readiness or escalation record where relevant
- Evidence location: source evidence in SYS-ECM-002 Compliance Reporting and Evidence Repository; target Hermes assessment record in Odoo under ISS-HERMES-001.
- Retention: according to the applicable approved policy and Bitkaya record-retention requirements.
- Testing method: inspect environment-readiness evidence and sample traceability from acceptance criteria to test cases
- Testing frequency: before each test cycle and after material environment change
Relationships
- Requirement: REQ-IT-007 Maintain Software Testing and Release Assurance
- Process: PRC-RSA-001 Resilience Systems and Assurance
- Procedure: PROC-COTS-003 Prepare Controlled COTS Test Environment and Test Design
Assurance
Runtime effectiveness results are maintained in Odoo and assessed through the Hermes workflow tracked in ISS-HERMES-001. This note defines design, ownership, evidence expectations and testing method; it does not contain a manually maintained operation, evidence or overall effectiveness rating.
- Design status: implemented design; runtime effectiveness pending system-derived assessment
History
- 2026-07-26: Normalized evidence metadata and separated design status from runtime effectiveness.
- 2026-07-26: Added the evidence-system relationship required for Hermes assessment mapping.
- 2026-07-26: Created from the approved COTS manual and mapped to CBCS-derived IT requirements.