coverage-analysis

Enforce a coverage ratchet threshold in CI to prevent coverage decreases. This approach tracks your current coverage baseline, fails pull requests that lower it, and ensures your test coverage metrics only increase over time.

Identify test coverage gaps by running Istanbul or V8 coverage reports in your Node.js project. This process highlights untested lines and branches, providing actionable insights to prioritize which specific code areas need new tests.

Yes, you can set per-directory coverage thresholds for JavaScript and TypeScript projects. This allows you to enforce different coverage requirements for various folders, ensuring critical modules meet higher coverage standards than others.

This coverage analysis works with both Vitest and Istanbul for JavaScript/TypeScript Node.js projects, as well as pytest for Python. It configures the respective coverage providers to generate reports and enforce ratcheting thresholds.

A PR coverage diff check analyzes code changes in a pull request to ensure new lines are adequately tested. It prevents untested code from merging by comparing the coverage report against the specific diff.

Distinguish meaningful test coverage from vanity coverage by analyzing branch coverage and enforcing a ratcheting threshold in CI. This methodology prioritizes actionable gap analysis over simply chasing high line coverage percentages.