test: assert.strictEqual parameters ordered correctly
The assert.strictEqual function should have the actual value first and the expected value second to enable easier debugging of AssertionErrors. PR-URL: https://github.com/nodejs/node/pull/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>
This commit is contained in:
parent
c5d0a48fb3
commit
0b0aeda2ce
@ -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();
|
||||
}));
|
||||
}));
|
||||
|
Loading…
x
Reference in New Issue
Block a user