-
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: minor fixes to test-module-loading.js #12728
Conversation
|
||
assert.ok(a.A instanceof Function); | ||
assert.strictEqual('A', a.A()); | ||
assert.strictEqual(false, false, 'testing the test program.'); |
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.
I see this was like this before, but is this supposed to be a comment? It will never fail as-is.
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.
That should probably be in test-assert.js
and inside an assert.doesNotThrow()
. Especially since this is a first-time contribution, I'm OK leaving it. Maybe we can open an issue for it and label it good first contribution
for someone else to fix. :-D
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.
(Or, alternatively, I'd be OK with the line simply being removed from this test.)
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.
Sorry for the late response. I got confused with it a little bit too. I agree with Trott this is not gaining coverage for testing module-loading. Putting it in comment will be an example of how to use strictEqual. I'll remove it then.
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.
The commit has been updated to remove the unnecessary assertion. I also updated the title of the commit to be in compliance with other PRs.
Use block scope for local variables only used in a small code block. Fixed inverse arguments in some usages of Assert.strictEqual.
@Trott Hi Rich, I've updated the commit associated with the pull request. Is there any steps I missed for this PR to go through? Again thank you for you help! |
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 if CI is green
Use block scope for local variables only used in a small code block. Fixed inverse arguments in some usages of Assert.strictEqual. PR-URL: nodejs#12728 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]>
Landed in 133fb0c. |
Use block scope for local variables only used in a small code block. Fixed inverse arguments in some usages of Assert.strictEqual. PR-URL: nodejs#12728 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]>
Should this be backported to |
Use block scope for local variables only used in a small code block.
Fixed inverse arguments in some usages of Assert.strictEqual.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)