create-verify-test-coverage

To verify test coverage before release, you need to execute tests with coverage collection and measure line coverage for changed projects. This confirms your changes are adequately tested rather than relying on assumptions.

Acceptance criteria validation checks that numbered acceptance criteria have corresponding tests using required story and AC trait mappings. It ensures every defined requirement is explicitly covered by automated tests before release.

You map acceptance criteria to tests using required story and AC trait mappings. This trait-based mapping validates that each numbered acceptance criterion has a corresponding test, confirming quality gates are met.

Test coverage verification applies to pull request preparation by running tests with coverage collection and reporting measured line coverage for changed projects. It helps QA workflows verify changes are gate-ready before deployment.

You need to run acceptance criteria coverage checks during story verification, pull request preparation, and release readiness checks. This ensures software changes have adequate test coverage and validates acceptance criteria before deployment.

Relying on measured coverage instead of assumptions prevents untested changes from reaching production. By measuring real coverage results and validating acceptance criteria coverage, teams confirm quality gates are genuinely met before release.