review-coverage

Test coverage gap analysis works by inspecting code changes against a baseline like origin/main. It quantifies untested logic introduced by modified or added files and functions, reporting missing test cases and edge conditions while enforcing a strictly read-only review workflow.

The best way to check test coverage for new code paths before merging is running a diff-based analysis on your local branch. This read-only process quantifies coverage gaps introduced by the changes and provides concrete recommendations to close them, reducing deployment risk.

Yes, you can use diff-based test coverage analysis for local branches. By comparing your current branch against a baseline such as origin/main, the review process inspects modified files and functions to quantify missing tests and edge cases without making any code changes.

This test coverage review workflow does not modify your source code. It enforces a strictly read-only analysis by inspecting diffs to report missing tests, edge cases, and concrete recommendations, ensuring your repository remains untouched during the pull request review process.

You need to quantify test coverage gaps by inspecting diffs when verifying that new or modified code paths are covered by tests. This process is essential during pre-merge checks and pull request reviews to reduce regressions and deployment risk introduced by code changes.