From 5bf919e818c09453afcf2469b79d337ff17db741 Mon Sep 17 00:00:00 2001 From: Ivan Lukasevych Date: Fri, 12 Oct 2018 10:39:25 -0700 Subject: [PATCH] test: fix assert.strictEqual() arguments order PR-URL: https://github.com/nodejs/node/pull/23539 Reviewed-By: James M Snell Reviewed-By: Colin Ihrig Reviewed-By: Gireesh Punathil Reviewed-By: Trivikram Kamat Reviewed-By: Ruben Bridgewater --- test/parallel/test-tls-set-encoding.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/test/parallel/test-tls-set-encoding.js b/test/parallel/test-tls-set-encoding.js index b3aa52a22a73f3..77cb5763aeecca 100644 --- a/test/parallel/test-tls-set-encoding.js +++ b/test/parallel/test-tls-set-encoding.js @@ -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(); });