In product development the supplier tests the product against approved test plans and specifications which, once run, show that every requirement, function and design element has been satisfied; testing may take one or several stages, for example module, integration and system testing, according to the product. The records of each stage are reviewed and approved, and kept for a period set in the QMS that lasts at least as long as the software version is supported. Failed tests are handled through a formal, documented process. Where the supplier configures a product or builds a custom application, it agrees with the regulated company how many test specifications there will be and in how much detail.
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.