Skip to content
Permalink
Browse files

test: fix order of arguments passed to strictEqual

The argument order in the strictEqual check was in the wrong order.
The first argument is now the actual value and the second argument is
the expected value.

PR-URL: #23571
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
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: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
  • Loading branch information...
eojthebrave authored and jasnell committed Oct 12, 2018
1 parent 2d86696 commit b49f4a93a60de7b0cd4e38e1ea4efa095e8a7e49
Showing with 2 additions and 2 deletions.
  1. +2 −2 test/parallel/test-net-socket-local-address.js
@@ -18,8 +18,8 @@ const server = net.createServer((socket) => {

server.on('close', common.mustCall(() => {
// client and server should agree on the ports used
assert.deepStrictEqual(clientLocalPorts, serverRemotePorts);
assert.strictEqual(2, conns);
assert.deepStrictEqual(serverRemotePorts, clientLocalPorts);
assert.strictEqual(conns, 2);
}));

server.listen(0, common.localhostIPv4, connect);

0 comments on commit b49f4a9

Please sign in to comment.
You can’t perform that action at this time.