-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feature Request: Add VSCode Coverage API Support #228
Comments
@sgtwilko The VSCode code coverage API is very new and still a work in progress. Once it firms up a bit I'll give it a shot as Pester does have code coverage output support. |
I've found a way to see coverage produced by pester, but it needs a configuration to be created. |
March 2024 release of VSCode has got the Code Coverage API support. I would really like to see this feature added for Pester tests. |
@Glober777 it's on the roadmap! I need to get thru conference season for now but I plan to start work on it after that. |
@Glober777 a temp fix for me was configuring pester to output a code coverage file, and using a different plugin to consume those files and display the results in the VScode gutter. |
Hiya,
Nice extension, thank you!
Is there a way we can see the code coverage as we can other extensions like the Jest extension?
The text was updated successfully, but these errors were encountered: