test: replace assert.throws with common.expectsError

[mithunsasidharan]

Refactored tests to replace assert.throws(fn, common.expectsError(err)); with common.expectsError(fn, err);

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

Affected core subsystem(s)

test

[mithunsasidharan]

@apapirovski @jasnell : Can I request if we could have this and other related PRs reviewed and landed sooner to avoid possible merge conflicts and changes resulting from other PRs ?

[apapirovski]

This shouldn't be too likely to run into merge conflicts since it modifies pretty specific code. IMO it'll need the usual 48 hours to land. I'll review later today or tomorrow when I've got a moment.

[mithunsasidharan]

@apapirovski : Thanks a lot. Here's ref to all 6 PRs related to this.. https://github.com/nodejs/node/pulls/mithunsasidharan

[apapirovski]

SGTM if the CI is green

[apapirovski]

CI: https://ci.nodejs.org/job/node-test-pull-request/11919/

[mithunsasidharan]

@apapirovski : Can we have this and related PRs 17497, 17494,17484,17483 merged so that we can avoid potential merge conflict issues and its already been over 2 days ! Kindly advice. Thanks !

[apapirovski]

@mithunsasidharan Please try to avoid pinging re: merging PRs. Someone will merge a PR if it's ready when they have a moment. As you'll note, there are over 180 open PRs and most of us are volunteers.

Also, strictly speaking only two of those PRs are over 48 hours old. This one still has another 4 hours to bake.

[mithunsasidharan]

@apapirovski : My sincere apologies. It was out of excitement and intend to avoid any possible merge conflict. I will keep up with the rules. Thanks again !

[apapirovski]

Would like to see a few more reviews for this so will wait to merge. If no one gets a chance to review in the next 24-48 hours, then will land as is.

[maclover7]

LGTM, do your PRs cover all remaining assert.throws instances? Is there an ESLint rule that should be introduced here?

[mithunsasidharan]

@maclover7 : The open PRs cover all remaining instances. Thanks !

[apapirovski]

@maclover7 I have a lint rule ready (it's in one of the Code & Learn threads and my gist account), will introduce it when I have a moment.

[apapirovski]

Landed in eae0c05

[gibfahn]

If someone would like to backport this to v8.x-staging and v6.x-staging, please follow the guide and raise backport PRs.