From 511d79dce0c1ca7d7b6e2533f53a2d29465903a8 Mon Sep 17 00:00:00 2001 From: jonask Date: Mon, 6 Nov 2017 17:28:03 +0200 Subject: [PATCH] remove message from test assertion assert message in strictEqual was hiding error why test has failed, it just showed what value is expected and in case of failure we want to know which value has caused test to fail --- test/parallel/test-child-process-spawnsync.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/parallel/test-child-process-spawnsync.js b/test/parallel/test-child-process-spawnsync.js index 7b768d8403ac07..6ff7b41edaba71 100644 --- a/test/parallel/test-child-process-spawnsync.js +++ b/test/parallel/test-child-process-spawnsync.js @@ -28,7 +28,7 @@ const spawnSync = require('child_process').spawnSync; // Echo does different things on Windows and Unix, but in both cases, it does // more-or-less nothing if there are no parameters const ret = spawnSync('sleep', ['0']); -assert.strictEqual(ret.status, 0, 'exit status should be zero'); +assert.strictEqual(ret.status, 0); // Error test when command does not exist const ret_err = spawnSync('command_does_not_exist', ['bar']).error;