From 35093eb07b924698377a5f5177267afef1c6c754 Mon Sep 17 00:00:00 2001 From: Matt Phillips Date: Thu, 1 Dec 2016 10:38:53 -0600 Subject: [PATCH] test: use assert.strictEqual and fix setTimeout Changes assert.equal to assert.strictEqual in two places and adds a second argument of 0 to setTimeout PR-URL: https://github.com/nodejs/node/pull/9957 Reviewed-By: James M Snell --- test/parallel/test-domain-timers.js | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/test/parallel/test-domain-timers.js b/test/parallel/test-domain-timers.js index faa57df1277083..d42afa7471791a 100644 --- a/test/parallel/test-domain-timers.js +++ b/test/parallel/test-domain-timers.js @@ -8,21 +8,22 @@ var timeout; var timeoutd = domain.create(); timeoutd.on('error', common.mustCall(function(e) { - assert.equal(e.message, 'Timeout UNREFd', 'Domain should catch timer error'); + assert.strictEqual(e.message, 'Timeout UNREFd', + 'Domain should catch timer error'); clearTimeout(timeout); })); timeoutd.run(function() { setTimeout(function() { throw new Error('Timeout UNREFd'); - }).unref(); + }, 0).unref(); }); var immediated = domain.create(); immediated.on('error', common.mustCall(function(e) { - assert.equal(e.message, 'Immediate Error', - 'Domain should catch immediate error'); + assert.strictEqual(e.message, 'Immediate Error', + 'Domain should catch immediate error'); })); immediated.run(function() {