test-coverage-gate

Enforce minimum test coverage thresholds before shipping by running a coverage gate on PRs, merges, and releases. The gate blocks shipping workflows when line, branch, or function coverage falls below configured thresholds.

Yes, test coverage gates work with Vitest, Jest, c8, and Istanbul. The gate auto-detects the active coverage tool in your project and runs the appropriate coverage analysis to evaluate against configured thresholds.

A coverage gate is a pre-ship check that enforces minimum test coverage thresholds before code is shipped. It blocks PR creation, merges, or releases when line, branch, or function coverage drops below the configured limits.

Configure test coverage thresholds by setting custom values for lines, branches, and functions. The coverage gate applies sensible default values, such as an 80% minimum, and blocks shipping when code coverage falls below your defined thresholds.

Blocking releases when test coverage falls below a certain percentage prevents untested code from reaching production. The coverage gate enforces minimum thresholds across lines, branches, and functions to maintain quality assurance before shipping.

Coverage gates enforce minimum thresholds for lines, branches, and functions but do not validate test logic or assert application behavior. They block shipping workflows based on coverage metrics alone, requiring existing test suites to generate the coverage data.