Skip to content

test(web): add v8 coverage with truthful baseline floor#26

Merged
offendingcommit merged 1 commit into
mainfrom
chore/vitest-coverage
May 28, 2026
Merged

test(web): add v8 coverage with truthful baseline floor#26
offendingcommit merged 1 commit into
mainfrom
chore/vitest-coverage

Conversation

@offendingcommit
Copy link
Copy Markdown
Owner

Adds code-coverage measurement with an honest, ratchetable floor:

  • @vitest/coverage-v8 (catalog-pinned at the vitest ^4 line).
  • test:coverage script, wired through turbo with inputs + coverage/** output so it shares the cache.
  • Thresholds set to a floor measured on main — lines 18 / functions 10 / branches 10 / statements 17 (current actuals: 19.3 / 11.4 / 11.7 / 18.9). The fork's 22% number was calibrated to its larger file set; I re-measured rather than copy it.
  • coverage/ gitignored.

The multi-job CI fan-out from the source branch was deliberately not included (it re-runs setup per job, which is cache-hostile).

Credit

Coverage config adapted from @BenSheridanEdwards's fork (chore/ci-hardening). Thanks Ben!

Verification

make check green; turbo run test:coverage passes the threshold gate.

Adds @vitest/coverage-v8 (catalog-pinned), a test:coverage script wired
through turbo (inputs + coverage/** output), and coverage thresholds set
to a floor measured on main (lines 18 / funcs 10 / branches 10 / stmts
17 against current 19.3/11.4/11.7/18.9). Ratchet upward as tests grow.

Adapts the coverage config from @BenSheridanEdwards's fork; the multi-job
CI fan-out from that branch was intentionally left out.

Co-authored-by: Ben Sheridan-Edwards <BenSheridanEdwards@users.noreply.github.com>
@offendingcommit offendingcommit force-pushed the chore/vitest-coverage branch from 949d9a4 to 94c4235 Compare May 28, 2026 19:21
@offendingcommit offendingcommit merged commit edc498d into main May 28, 2026
2 checks passed
@offendingcommit offendingcommit deleted the chore/vitest-coverage branch May 28, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant