-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
test: Refactors test/parallel/test-async-wrap-post-did-throw.js #8625
Conversation
…s. Replaces equal method on assert module to strictEqual.
* commit 'a89c23f8ebb8d47e2f577d3594bfb465c1861d25': (30 commits) test: improve test-https-agent.js test: fix test-debug-signal-cluster.js flakyness benchmark: ignore significance when using --runs 1 inspector: fix tests on Windows doc/json: make sure links are correctly passed to marked repl: improve .help message test: make test-tick-processor.js non-flaky doc: link onboarding to contributing guide test: add coverage for client._addHandle() 2016-09-14, Version 6.6.0 (Current) doc: remove duplicate content from readline doc timers: remove unreachable code doc: capitalize arguments' type names in url doc doc: add gibfahn to collaborators doc: add imyller to collaborators doc: standardize rest parameters test: fix flaky test-force-repl inspector: listen on process.debugPort doc: add not-an-aardvark to collaborators doc: link SIGTSTP / SIGCONT events in readline doc ...
LGTM. Would you care to squash the commits? |
Probably not worthwhile if it conflicts with #8531 in any significant way? |
I'd say it's still worthwhile even if the test ends up getting refactored by #8531. This is one of the commits coming from the code and learn over the weekend and the primary intent is to not only help improve the codebase but help new contributors through the process of getting a PR landed. I'm sure that any potential conflict that arises from this PR is likely quite minimal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Right now this doesn’t conflict with the async-hooks PR anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* change var to let * replace equal with strictEqual PR-URL: #8625 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in 0a9f56a. Thank you! |
Thank you all for your help. Really appreciated. |
* change var to let * replace equal with strictEqual PR-URL: #8625 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
* change var to let * replace equal with strictEqual PR-URL: #8625 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
Checklist
Affected core subsystem(s)
?
Description of change
This changes var to let in test/parallel/test-async-wrap-post-did-throw.js. Replaces equal method on assert module to strictEqual.