Make a coverage threshold that fails the build

The coverage number in my terminal says 40%. My CI job still turns green.

Intermediate to advancedRead 5 minDoing: about 30 minutes6 steps

▶ Start

What you'll have at the end

A coverage threshold that exits red the moment coverage drops below it, proven with one deliberate drop

Before you start

You need

A Vitest suite with coverage already turned on and printing a report on every run, testing a checkout module's discount math but never importing a separate, completely untested receipt-formatting file, with no coverage floor configured yet.

Not covered

Enforcing the same floor on every single file rather than the whole project's average, a stricter setting worth reaching for once the team already trusts the project-wide gate.

Leans on

6 steps

Where to go next

The same test fails in CI and passes on your laptop

when the pipeline's inconsistency is a flaky timing race, not an unenforced coverage number that never fails anything

Checked 25 Aug 2026

Part of the Vitest Testing Framework cookbook