Add test coverage reporting - #24
Closed
dyk1454683243-sudo wants to merge 2 commits into
Closed
dyk1454683243-sudo wants to merge 2 commits into
dyk1454683243-sudo wants to merge 2 commits into
Conversation
Add npm run test:coverage using Node's built-in test coverage, persist the per-file table, and upload it as a CI artifact. No percentage gate. Co-authored-by: David <dyk1454683243-sudo@users.noreply.github.com>
|
@cursoragent is attempting to deploy a commit to the solabode499-5056's projects Team on Vercel. A member of the Team first needs to authorize it. |
The all-files totals are the same locally and in CI, so drop the unnecessary drift caveat. Co-authored-by: David <dyk1454683243-sudo@users.noreply.github.com>
Contributor
Author
|
Withdrawing this PR while I clean up a high-volume open-PR backlog. Sorry for the noise — happy to come back later with a focused change if useful. |
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
2 participants
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.
What does this PR do?
Adds coverage reporting on top of the existing
node --testsuite, without a new dependency or a percentage gate.npm run test:coveragerunsnode --test --experimental-test-coverageviascripts/coverage-report.jsand writes the per-file table tocoverage/coverage.txt(gitignored).npm testso the suite still fails the job on a broken test, then uploads the text report as thecoverage-reportartifact. There is no line/branch/function threshold.docs/development.mddocuments how to run it, how to read the table, and the current baseline (~67% lines / ~83% branches / ~63% functions).The script is named
coverage-report.json purpose: Node's default test globs includetest-*.js, so a file calledtest-coverage.jswould be picked up as a test.Related Issue
Fixes #12
Type of Change
Screenshots
Not a UI change.
Checklist