Skip to content
Permalink
Browse files

test: fix test-cli-syntax assertions on windows

The test introduced in a5f91ab
accidentally introduced failures on some windows builds. Update the
assertion that was causing the failures.

PR-URL: #12212
Ref: #11689
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
  • Loading branch information...
not-an-aardvark committed Apr 4, 2017
1 parent c79b081 commit 9348f31c2aec996cf6cf7731244b2d76153440ea
Showing with 4 additions and 3 deletions.
  1. +4 −3 test/parallel/test-cli-syntax.js
@@ -124,9 +124,10 @@ syntaxArgs.forEach(function(args) {
const args = [checkFlag, evalFlag, 'foo'];
const c = spawnSync(node, args, {encoding: 'utf8'});

assert.strictEqual(
c.stderr,
`${node}: either --check or --eval can be used, not both\n`
assert(
c.stderr.startsWith(
`${node}: either --check or --eval can be used, not both`
)
);

assert.strictEqual(c.status, 9, 'code === ' + c.status);

0 comments on commit 9348f31

Please sign in to comment.
You can’t perform that action at this time.