Fetch Test Coverage

[ronag]

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.

[teezzan]

@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?

[ronag]

Run ’npm run coverage’ see what parts of the code lacks test and make one in the test folder.

[trivikr]

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

[mcollina]

Could you propose some text?

[trivikr]

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:

• docs: link to fetch test coverage issue #1191
• docs: add test commands in CONTRIBUTING.md #1192

[mcollina]

Done!