Enforce test coverage thresholds in CI#135
Merged
Merged
Conversation
Adds V8 coverage to the vitest run with a test:coverage script and wires it into verify, so the gate applies locally and in CI. Thresholds are set a few points below current coverage (statements/lines/functions 95, branches 90) as a floor against regressions.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds V8 coverage to the vitest run and enforces minimum thresholds so coverage can't silently regress. Coverage runs as part of
verify, which CI already invokes.How verified
pnpm test:coverageenforces thresholds (statements/lines/functions 95, branches 90) and passes at current coverage (~98/95/98/98).pnpm verifyruns coverage and passes locally.Closes #134