feat(vitest-runner): report test locations - #6188
Open
christopher-buss wants to merge 1 commit into
Open
Conversation
Enable vitest's `includeTaskLocation` and translate the reported task location into the `startPosition` that the test runner API already carries, and that the jest-runner and cucumber-runner report today. Incremental mode uses the test locations to diff test files. Without them, Stryker has to assume that every test in a changed test file changed, so it reruns every mutant covered by that file. With them, only the mutants covered by the tests that actually changed are rerun. This moves the vitest runner from "tests per file without location" to "full" test reporting. Stryker stores 0-based lines and columns internally. Vitest builds the location from a V8 stack trace, so both its line and its column are 1-based, and both are decremented. The jest-runner decrements the line only, because jest takes its columns from babel, where they are already 0-based. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Enable vitest's
includeTaskLocationand translate the reported task location into thestartPositionthat the test runner API already carries, and that the jest-runner and cucumber-runner report today.Incremental mode uses the test locations to diff test files. Without them, Stryker has to assume that every test in a changed test file changed, so it reruns every mutant covered by that file. With them, only the mutants covered by the tests that actually changed are rerun. This moves the vitest runner from "tests per file without location" to "full" test reporting.
Stryker stores 0-based lines and columns internally. Vitest builds the location from a V8 stack trace, so both its line and its column are 1-based, and both are decremented. The jest-runner decrements the line only, because jest takes its columns from babel, where they are already 0-based.
Closes #6186.
AI Attribution:
Assisted via Claude Code but reviewed and filed by myself.