Repository navigation
dns.promises test coverage is poor #22471
Copy link
Copy link
Closed
Labels
dnsIssues and PRs related to the dns subsystem.Issues and PRs related to the dns subsystem.experimentalIssues and PRs related to experimental features.Issues and PRs related to experimental features.promisesIssues and PRs related to ECMAScript promises.Issues and PRs related to ECMAScript promises.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
- addeddnsIssues and PRs related to the dns subsystem.Issues and PRs related to the dns subsystem.promisesIssues and PRs related to ECMAScript promises.Issues and PRs related to ECMAScript promises.experimentalIssues and PRs related to experimental features.Issues and PRs related to experimental features.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
on Aug 23, 2018 #21559 should partially (?) fix this, I presume.
- addedhelp wantedIssues that need assistance from volunteers or PRs that need help to proceed.Issues that need assistance from volunteers or PRs that need help to proceed.
on Aug 23, 2018 Willing to work towards this, with some mentoring/help. For example, would a
common.dnsTest()be helpful here, similar tocommon.fsTest()from #20439?@ChALkeR I will be happy to contribute in this issue.
Is there is an existing test file or should i create a new one (and if so - in which libary under "test"?)It's considerably less poor now that we run
internettests during coverage report generation. Right now, it's at 64 of 67 branches. Prior to that, it was 40 of 67.I'd welcome someone getting those last 3 branches covered, but I think this can nonetheless be closed at this time.
- removedhelp wantedIssues that need assistance from volunteers or PRs that need help to proceed.Issues that need assistance from volunteers or PRs that need help to proceed.
on Sep 18, 2018 I'm going to close this. Feel free to re-open if you think that's not warranted at this time, @ChALkeR.
Metadata
Metadata
Assignees
Labels
dnsIssues and PRs related to the dns subsystem.Issues and PRs related to the dns subsystem.experimentalIssues and PRs related to experimental features.Issues and PRs related to experimental features.promisesIssues and PRs related to ECMAScript promises.Issues and PRs related to ECMAScript promises.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Ref: #20435 (comment)
Experimental
dns/promisesAPI is present in the currentmasterwithout proper test coverage.According to the coverage report, the following functions are not tested at all:
onlookuponlookupallonlookupservicecreateLookupServicePromiseWhile inspecting the experimental
fs.promises, there were also some implementation bugs found that could have been caught by code coverage, see e.g. #20407. Thedns.promisesis much smaller in lines of code, but it is still possible that it contains bugs that could be noticed by extending coverage.