From 74e99528492065001b4929cdc1fb60942019acc3 Mon Sep 17 00:00:00 2001 From: Salman Shakeel Date: Fri, 12 Oct 2018 14:16:51 -0400 Subject: [PATCH] test: reversed actual and expected values for .strictEqual() Fixed strictEqual() parameters order according to the documentation for the assertion. Refs: https://nodejs.org/dist/latest-v10.x/docs/api/assert.html#assert_assert_strictequal_actual_expected_message --- test/parallel/test-next-tick-ordering.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/parallel/test-next-tick-ordering.js b/test/parallel/test-next-tick-ordering.js index 76f43efa932fbf..9ae212cb7f3fbe 100644 --- a/test/parallel/test-next-tick-ordering.js +++ b/test/parallel/test-next-tick-ordering.js @@ -47,7 +47,7 @@ console.log('Running from main.'); process.on('exit', function() { - assert.strictEqual('nextTick', done[0]); + assert.strictEqual(done[0], 'nextTick'); /* Disabling this test. I don't think we can ensure the order for (i = 0; i < N; i += 1) { assert.strictEqual(i, done[i + 1]);