feat(lsp): support test coverage visualization#35197
Open
dmthong181096 wants to merge 1 commit into
Open
Conversation
Deno Individual Contributor License AgreementAll contributors have signed the CLA. Thank you! This is an automated message from CLA Assistant |
Author
|
/try |
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.
/claim #18147
Description
This pull request implements native test coverage visualization in Deno's LSP by adding support for the custom
deno/testCoveragenotification (resolves #18147). This allows editor extensions (such as the Deno VS Code extension) to render line coverage gutters.Key Changes
TestCoverageNotificationtypes and routing in the client notification dispatcher.collect_coverage_reportsto allow programmatic in-memory collection of results (retaining accurate sourcemap translations to original TypeScript source lines).kind: "coverage"runs, parse them asynchronously, and dispatch the line hit counts to the editor.lsp_testing_api_coverageintests/integration/lsp_tests.rsto verify that executing tests with the coverage option correctly emits notifications containing line coverage hit counts.Verification
cargo test -p integration_tests lsp_testing_api