test: fix assert.strictEqual() arguments order

PR-URL: https://github.com/nodejs/node/pull/23539
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:
Ivan Lukasevych 2018-10-12 10:39:25 -07:00 committed by Ruben Bridgewater
parent 3c2f9ad0a1
commit c5d0a48fb3
No known key found for this signature in database
GPG Key ID: F07496B3EB3C1762

View File

@ -64,15 +64,15 @@ server.listen(0, function() {
// readyState is deprecated but we want to make
// sure this isn't triggering an assert in lib/net.js
// See https://github.com/nodejs/node-v0.x-archive/issues/1069.
assert.strictEqual('closed', client.readyState);
assert.strictEqual(client.readyState, 'closed');
// Confirming the buffer string is encoded in ASCII
// and thus does NOT match the UTF8 string
assert.notStrictEqual(buffer, messageUtf8);
assert.notStrictEqual(messageUtf8, buffer);
// Confirming the buffer string is encoded in ASCII
// and thus does equal the ASCII string representation
assert.strictEqual(buffer, messageAscii);
assert.strictEqual(messageAscii, buffer);
server.close();
});