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
deno coverage
umbrella issue
#12826
Comments
Also these two likely related issues with accuracy where testing individual files shows different coverage to testing multiple files: |
Thanks @zandaqo I added them to the list. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Not stale. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Not stale. |
Just FYI, line counts and branch detection are still broken today with the most recent Deno (v1.30.0); see #9865. |
Umbrella issue for all the reported quirks and suggestions to
deno coverage
:deno coverage
#9669deno test --coverage
doesn't seem accurate #9754deno coverage
line and branch counts are incorrect #9865deno test --coverage
generates invalid JSON in certain conditions that breaksdeno coverage
#12112deno coverage --unstable --lcov
causes panic in ubuntu runner in deno_std ci #10420deno coverage
errors with type error if the source code uses custom "lib" configuration #13326deno coverage
shouldn't run type checks #13161The text was updated successfully, but these errors were encountered: