Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: view test coverage in editor #18147

Open
KnorpelSenf opened this issue Mar 12, 2023 · 4 comments
Open

feat: view test coverage in editor #18147

KnorpelSenf opened this issue Mar 12, 2023 · 4 comments
Labels
feat new feature (which has been agreed to/accepted) help wanted community help requested lsp related to the language server testing related to deno test and coverage

Comments

@KnorpelSenf
Copy link
Contributor

Deno

  • can run tests.
  • can generate test coverage reports.
  • has an an editor integration (LSP).

It would be amazing if VSCode would display the test coverage right inside the editor.

The line coverage results are very useful when writing tests because they let me easily see which case are covered by tests and which ones are not. However, every time I add a test to cover some more code, I need to run deno test and deno coverage and then reload my browser window.

I am aware that there are third-party tools that should be able to consume the LCOV output and do this, but I would prefer if it would “just work” without any additional configuration.

@bartlomieju
Copy link
Member

Seems like a useful feature and I would gladly accept a PR for this, but the core team doesn't have a bandwidth to work on this for a forseeable future.

@bartlomieju bartlomieju added feat new feature (which has been agreed to/accepted) lsp related to the language server testing related to deno test and coverage help wanted community help requested labels Mar 12, 2023
@KnorpelSenf
Copy link
Contributor Author

KnorpelSenf commented Dec 10, 2023

Since you are now focusing on making test coverage more easily accessible, such as via deno coverage --html, would you reconsider this feature request?

@KnorpelSenf
Copy link
Contributor Author

@bartlomieju how should the user experience be for this? Do people need to run deno test from the command line and then the lsp picks up the output files? I don't want to simply execute the test files in the background all the time in order to update the coverage, that seems too opaque.

@nabby27
Copy link

nabby27 commented Sep 27, 2024

I would like to see this feature, it would be super useful. I have created a $70 bounty for whoever implements it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat new feature (which has been agreed to/accepted) help wanted community help requested lsp related to the language server testing related to deno test and coverage
Projects
None yet
Development

No branches or pull requests

3 participants