-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: change assert.equal to assert.strictEqual #9956
Conversation
First line of commit message is too long, see the commit message guidelines here. |
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. The commits will need to be squashed and a new-line needs to be added at the end of the file to pass linting.
ping @crokita: Can you add a newline to the end of the file? Even better if you can squash the commits into a single commit, but that can also be done by whoever lands the change. |
bde2cce
to
30d5451
Compare
Yep! Updated the branch. Does this look okay @Trott ? |
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 ✅
Landed 70d752e |
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
Thanks for the contribution @crokita! 🎉 |
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
Checklist
make -j8 test
(UNIX)Affected core subsystem(s)
test
Description of change
Use assert.strictEqual() instead of assert.equal() for lines 11, 12, 13, 14, 21, 22, 23, 24, 28