A test plan built on enterprise-wide standards sets out roles and responsibilities and the criteria for entering and leaving testing, and the relevant parties approve it: the plan is consistent with the programme and project quality plan and organisational standards and is drawn up with process owners and IT stakeholders; it reflects the project's risk assessment and covers every functional and technical requirement, with testing more rigorous where the consequences of system faults and failure are greater; it deals with any requirement for test results to be accredited, internally or externally, to meet financial or regulatory requirements; it names the resources needed to run tests and evaluate the results; it identifies the right testing stages (unit, system, integration, user acceptance, performance, stress, data conversion, security, operational readiness, backup and recovery); it considers test preparation, training, setting up the test environment, planning and documenting tests, handling and correcting errors, and formal approval; it is approved by stakeholders, process owners and IT among them; and it sets clear success criteria for every testing stage, agreed with process owners and IT.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.