-
Notifications
You must be signed in to change notification settings - Fork 512
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
Fetch Test Coverage #951
Comments
@ronag, I would love to work on this. However, I am a little new to this. Can you give me more information about the issue and a little bit of direction? |
Run ’npm run coverage’ see what parts of the code lacks test and make one in the test folder. |
I landed on this issue after reading about lack of test coverage in nodejs/node#41749 (comment) Assuming this is a tracking issue to improve test coverage, would it be helpful to provide detailed instructions on how folks can help in the issue description? cc @ronag Also, it would be helpful if a link to this issue is provided in README at https://github.com/nodejs/undici#undicifetchinput-init-promise |
Could you propose some text? |
How about this for issue description? Please refer lib/fetch folder on CodeCov to check which components of fetch implementation lack unit tests. Comment on this issue on which component you would like to add test and post a PR! Please refer CONTRIBUTING.md on how to run tests. I've posted the following PRs to improve discoverability/documentation: |
Done! |
This adds coverage for https://github.com/nodejs/undici/blob/abf7c4547d1a1aa9e023c0536a890bc0aa183f48/lib/fetch/file.js#L71. Refs: nodejs#951 Signed-off-by: Darshan Sen <raisinten@gmail.com>
Sent #1206 to complete the coverage of the |
any updates on this becoming stable? |
@KhafraDev, any idea on the coverage stats from wpt? |
I couldn't get any tools to work with it, but it's likely pretty high with the current test coverage. edit: I actually got c8 to work, but I'm unsure if it takes coverage from all 4 wpt suites. I'll need to configure it some more and do some testing. |
Would be great if we could show off your hard work with numbers! If nothing else to bring trust and confidence to our users. |
ran with current code cov for lib/fetch: ~92% if we can update codecov to combine all coverage files we'll likely see some increase? |
I'm going to close this, we definitely have adequate test coverage. |
Current test coverage on fetch is too low for a stable release.
Please refer lib/fetch folder on CodeCov to check which components of fetch implementation lack unit tests. Comment on this issue on which component you would like to add test and post a PR!
Please refer CONTRIBUTING.md on how to run tests.
The text was updated successfully, but these errors were encountered: