test: test-crypto-domain.js - assert.equal -> assert.strictEqual#10067
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
julianduque added crypto 
davidmarkclements changed the title changes assert.equal to assert.strictEqual to ensure specificity
cjihrig approved these changes Dec 1, 2016
addaleax approved these changes Dec 2, 2016
Member
addaleax commented Dec 2, 2016
Member
addaleax commented Dec 4, 2016
Landed in 26f0aec, thanks for the PR! |
addaleax pushed a commit that referenced this pull request Dec 4, 2016
changes assert.equal to assert.strictEqual to ensure specificity PR-URL: #10067 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
addaleax pushed a commit that referenced this pull request Dec 5, 2016
changes assert.equal to assert.strictEqual to ensure specificity PR-URL: #10067 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
addaleax pushed a commit to addaleax/node that referenced this pull request Dec 8, 2016
changes assert.equal to assert.strictEqual to ensure specificity PR-URL: nodejs#10067 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
jmdarling pushed a commit to jmdarling/node that referenced this pull request Dec 8, 2016
changes assert.equal to assert.strictEqual to ensure specificity PR-URL: nodejs#10067 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
MylesBorins pushed a commit that referenced this pull request Dec 20, 2016
changes assert.equal to assert.strictEqual to ensure specificity PR-URL: #10067 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
MylesBorins pushed a commit that referenced this pull request Dec 21, 2016
changes assert.equal to assert.strictEqual to ensure specificity PR-URL: #10067 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
MylesBorins pushed a commit that referenced this pull request Dec 21, 2016
changes assert.equal to assert.strictEqual to ensure specificity PR-URL: #10067 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
make -j8 test(UNIX), orvcbuild test nosign(Windows) passesAffected core subsystem(s)
test, crypto
Description of change
changes assert.equal to assert.strictEqual to ensure specificity
edit: correct subsystem