We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
V8 offers the possibility to generate code coverage ref: https://v8.dev/blog/javascript-code-coverage#for-embedders
I've already started writting a lcov parser : https://github.com/zekth/deno-lcov (ATM use standard lcov file but can be ported to v8 coverage files)
I think it would be really usefull for deno_std test modules and even for the core js of deno, to see what is really tested or not.
deno_std
core js
The text was updated successfully, but these errors were encountered:
Duplicate of #106
Sorry, something went wrong.
No branches or pull requests
V8 offers the possibility to generate code coverage
ref: https://v8.dev/blog/javascript-code-coverage#for-embedders
I've already started writting a lcov parser : https://github.com/zekth/deno-lcov (ATM use standard lcov file but can be ported to v8 coverage files)
I think it would be really usefull for
deno_std
test modules and even for thecore js
of deno, to see what is really tested or not.The text was updated successfully, but these errors were encountered: