build: upgrade vitest to 4.1.0, dynamic coverage badge#515
Merged
Conversation
4ad7801 to
0c554a3
Compare
Upgrade vitest and @vitest/coverage-v8 to 4.1.0. Add coverage summary generation script (scripts/generate-coverage-summary.mjs) that produces docs/releases/coverage-summary.json for a dynamic Shields badge. Update README badges to brightgreen and add coverage.
Add coverage_provider, scope, and excluded_suites fields to the generated coverage-summary.json for audit transparency. Makes clear that perf tests are excluded from coverage instrumentation runs.
65dfea2 to
677ddeb
Compare
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
scripts/generate-coverage-summary.mjsthat runs vitest with coverage and writesdocs/releases/coverage-summary.jsonScope
Dev tooling only. No runtime, protocol, or test behavior changes.
Coverage scope
Perf tests (
tests/perf/**) are excluded from coverage runs because coverage instrumentation overhead causes SLO threshold assertions to fail. The generatedcoverage-summary.jsonincludes explicit metadata:{ "coverage_provider": "@vitest/coverage-v8", "scope": "non-perf", "excluded_suites": ["tests/perf/**"] }Hidden Unicode check
All changed files scanned with
scripts/find-invisible-unicode.mjs: no dangerous Unicode found. GitHub's warning banner on the PR is a false positive frompnpm-lock.yamlintegrity hashes.Validation
node scripts/generate-coverage-summary.mjsproduces correct JSON (lines 80.98%)find-invisible-unicode.mjsclean on all changed files