Skip to content

Commit

Permalink
test: assert.strictEqual parameters ordered correctly
Browse files Browse the repository at this point in the history
The assert.strictEqual function should have the actual
value first and the expected value second to enable
easier debugging of AssertionErrors.

PR-URL: #23538
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
  • Loading branch information
jdenbroeder authored and rvagg committed Nov 28, 2018
1 parent 27fdf87 commit 766d8f0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion test/parallel/test-tls-securepair-server.js
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ server.listen(0, common.mustCall(function() {
client.stdout.pipe(process.stdout, { end: false });

client.on('exit', common.mustCall(function(code) {
assert.strictEqual(0, code);
assert.strictEqual(code, 0);
server.close();
}));
}));
Expand Down

0 comments on commit 766d8f0

Please sign in to comment.