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: #9957 Reviewed-By: James M Snell <[email protected]>
nodejs · Dec 21, 2016 · 93733cb · 93733cb
1 parent 45f553e
commit 93733cb
Showing 1 changed file with 5 additions and 4 deletions.
diff --git 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() {