CAPM Practice: Validate requirements through product delivery

Requirements test coverage measures whether all requirements have corresponding validation tests. Uncovered requirements (no test case) represent validation gaps — features may have been implemented but never formally validated against requirements, creating risk of undetected failures.

**Why not B:** Physical coverage of test environments across geographic regions relates to infrastructure deployment, not requirements test coverage. Test coverage in requirements validation measures whether each requirement has at least one corresponding test case to validate it.

**Why not C:** The percentage of code lines executed during testing is code coverage, not requirements test coverage. While code coverage measures how much source code is exercised by tests, requirements test coverage measures how many requirements have corresponding validation tests.

**Why not D:** The number of testing environments used is an infrastructure concern, not a measure of requirements coverage. Having multiple environments does not indicate whether all requirements have been validated — a single environment can provide full requirements coverage.