test: cover path coverage utilities - #997
Open
mgalore wants to merge 1 commit into
Open
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
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.
What changed and why
Adds focused unit coverage for
calculatePathCoverageandformatDependencyPath, including complete/partial coverage, missing or empty paths, order- and length-sensitive matching, and formatting edge cases.Closes #995
Verification
npm test -- tests/utils/path-coverage.test.tsnpm run lint:testsnpm run buildnpm test(upstream baseline has the same 6 offline-advisory-dependent failing suites / 29 failures; the new focused suite passes)