| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sorry, something went wrong.
|
This is currently marked as draft until the next semver-minor release of Node.js |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
This is my first feedback, I think the introduction should be improved to put it in context. It should be remembered that the learn section is intended for non-experts.
Sorry, something went wrong.
|
Deployment failed with the following error: The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM !
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for writing this, reads well
Sorry, something went wrong.
|
I've undrafted this, as the release proposal for v22.8.0 is ready at nodejs/node#54560, but it still shouldn't land until that does. The expected release date is 2024-08-26 2024-09-02 |
Sorry, something went wrong.
Unit Test Coverage Report
Unit Test Report
|
Sorry, something went wrong.
There was a problem hiding this comment.
this is great - looking forward to it
Sorry, something went wrong.
|
Can we have last review form @nodejs/test_runner |
Sorry, something went wrong.
There was a problem hiding this comment.
This is amazing. However I'm not sure we should be landing this before having stabilized the code coverage functionality.
Sorry, something went wrong.
There was a problem hiding this comment.
This is amazing. However I'm not sure we should be landing this before having stabilized the code coverage functionality.
Sorry, something went wrong.
|
I think this is okay to land once v22.8.0 releases, as it specifies that the --experimental-code-coverage command is needed, indicating that it is experimental. Would you like me to add a notice at the beginning that this is experimental, or just hold off until it's stabilized? |
Sorry, something went wrong.
|
I think it's better to hold off until it's stable. |
Sorry, something went wrong.
|
Is there an ETA for the stabilization of it? |
Sorry, something went wrong.
|
IMO code coverage (w/o the --enable-source-maps flag) is pretty stable. I haven't seen many bugs with it in a while. I asked a few weeks ago, and it was pointed out that statement coverage isn't supported, however, I'm not sure if that's in the plans for the immediate future of code coverage. The original issue tracking the stability has been closed as completed, as all tasks were completed, which might mean it's ready to be stable. I've left a comment asking. |
Sorry, something went wrong.
|
I'm fine keeping this open for the meantime, the problem is it becoming stale. |
Sorry, something went wrong.
|
I'm also happy to close and reopen it, as chances are there will be some significant changes to the coverage reporter before stabilization, and this only collecting merge conflicts. |
Sorry, something went wrong.
There was a problem hiding this comment.
@avivkeller has there been any change yet? I feel we could merge the PR to be honest.
Sorry, something went wrong.
|
It's still experimental, but it's more stable, so I also think this can be merged. @mcollina are you still blocking? (I'll resolve the conflicts later today) |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
Co-authored-by: Michael Esteban <mickel13@gmail.com> Signed-off-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
Signed-off-by: Aviv Keller <redyetidev@gmail.com>
|
Lighthouse Results
|
Sorry, something went wrong.
|
Article published: https://nodejs.org/en/learn/test-runner/collecting-code-coverage |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
This PR introduces a learning article on collecting code coverage in Node.js. However, it should not be merged until support for thresholds is included in the next semver-minor release, which is expected to be next week.
Related Issues
Support for code coverage: nodejs/node#46017
Support for code coverage inclusion/exclusion: nodejs/node#53553
Support for code coverage thresholds: nodejs/node#54429
Check List