Skip to content
Permalink
Browse files

test: add mustCall() to test-inspector-contexts

In test-inspector-contexts, if mainContextPromise is modified such that
the `method` argument is changed to something invalid, the test still
passes and the second part of the test never runs. Use
`common.mustCall()` to cause the test to fail if the second part of the
test does not run.

Refs: #30519 (comment)

PR-URL: #30649
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Denys Otrishko <shishugi@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
  • Loading branch information
Trott authored and MylesBorins committed Nov 26, 2019
1 parent f5ac4ec commit c3ad977867e5f41ea58dd57ad19f386f476487a9
Showing with 1 addition and 1 deletion.
  1. +1 −1 test/sequential/test-inspector-contexts.js
@@ -155,4 +155,4 @@ async function testBreakpointHit() {
await pausedPromise;
}

testContextCreatedAndDestroyed().then(testBreakpointHit);
testContextCreatedAndDestroyed().then(common.mustCall(testBreakpointHit));

0 comments on commit c3ad977

Please sign in to comment.
You can’t perform that action at this time.