Repository navigation
test: add source-level Jest coverage - #153
Merged
Merged
Conversation
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
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.
Problem
Existing Jest tests load the built parser from
dist/. Their coverage does not measure the TypeScript source directly.Changes
Validation
dist/, then runpnpm run test:source: 10 tests pass.pnpm run test:coverage: source files appear in the report.pnpm test: 2024 existing tests and 10 source tests pass.git diff --check: no errors.Local coverage on Node.js 24 is 79.67% lines and 67.22% branches. The report records 67.99% lines in
build-source-map.ts. CI will run coverage on Node.js 22.No sensitive data was added or redacted.
Closes #152