FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

feat(learn): Collecting code coverage by avivkeller · Pull Request #7006 · nodejs/nodejs.org · GitHub

feat(learn): Collecting code coverage - #7006

Merged
avivkeller merged 6 commits into
nodejs:mainfrom
avivkeller:code-coverage-learn
Mar 22, 2025
Merged

feat(learn): Collecting code coverage#7006
avivkeller merged 6 commits into
nodejs:mainfrom
avivkeller:code-coverage-learn

Conversation

Copy link
Copy Markdown
Member

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

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npm run format to ensure the code follows the style guide.
  • I have run npm run test to check if all tests are passing.
  • I have run npx turbo build to check if the website builds without errors.
  • [N/A] I've covered new added functionality with unit tests if necessary.

vercel Bot commented Aug 24, 2024
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Mar 22, 2025 1:36pm

Copy link
Copy Markdown
Member Author

This is currently marked as draft until the next semver-minor release of Node.js

Copy link
Copy Markdown
Member Author

AugustinMauroy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

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.

vercel Bot commented Aug 24, 2024

Copy link
Copy Markdown

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.

AugustinMauroy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM !

mikeesto left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Thanks for writing this, reads well

avivkeller marked this pull request as ready for review August 25, 2024 23:35
avivkeller requested a review from a team as a code owner August 25, 2024 23:35

avivkeller commented Aug 25, 2024
edited
Loading

Copy link
Copy Markdown
Member Author

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

github-actions Bot commented Aug 26, 2024
edited
Loading

Copy link
Copy Markdown
Contributor

Unit Test Coverage Report

Lines Statements Branches Functions

88.75% (742/836) 76.1% (242/318) 87.65% (142/162)

Unit Test Report

Tests Skipped Failures Errors Time
182 0 💤 0 ❌ 0 🔥 6.096s ⏱️

bmuenzenmeyer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

this is great - looking forward to it

Copy link
Copy Markdown
Member

Can we have last review form @nodejs/test_runner

mcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This is amazing. However I'm not sure we should be landing this before having stabilized the code coverage functionality.

mcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This is amazing. However I'm not sure we should be landing this before having stabilized the code coverage functionality.

Copy link
Copy Markdown
Member Author

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?

mcollina commented Sep 2, 2024

Copy link
Copy Markdown
Member

I think it's better to hold off until it's stable.

AugustinMauroy added content Issues/pr concerning content learn Issues/pr concerning the learn section labels Sep 12, 2024

ovflowd commented Oct 28, 2024

Copy link
Copy Markdown
Member

Is there an ETA for the stabilization of it?

Copy link
Copy Markdown
Member Author

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.

ovflowd commented Nov 17, 2024

Copy link
Copy Markdown
Member

I'm fine keeping this open for the meantime, the problem is it becoming stale.

Copy link
Copy Markdown
Member Author

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.

ovflowd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@avivkeller has there been any change yet? I feel we could merge the PR to be honest.

avivkeller commented Mar 22, 2025
edited
Loading

Copy link
Copy Markdown
Member Author

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)

mcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

lgtm

avivkeller and others added 4 commits March 22, 2025 09:26
Signed-off-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
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>

github-actions Bot commented Mar 22, 2025
edited
Loading

Copy link
Copy Markdown
Contributor

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 93 🟢 100 🟢 100 🟢 91 🔗
/en/about 🟢 100 🟢 100 🟢 100 🟢 91 🔗
/en/about/previous-releases 🟢 100 🟢 100 🟢 100 🟢 92 🔗
/en/download 🟢 92 🟢 100 🟢 100 🟢 91 🔗
/en/blog 🟢 99 🟢 100 🟢 96 🟢 92 🔗

avivkeller added the github_actions:pull-request Trigger Pull Request Checks label Mar 22, 2025
github-actions Bot removed the github_actions:pull-request Trigger Pull Request Checks label Mar 22, 2025
avivkeller added this pull request to the merge queue Mar 22, 2025
Merged via the queue into nodejs:main with commit a42315e Mar 22, 2025
avivkeller deleted the code-coverage-learn branch March 22, 2025 13:44

Copy link
Copy Markdown
Member Author

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content Issues/pr concerning content learn Issues/pr concerning the learn section

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants


Back | FazBrowse Home | New Git URL