`polymer test -v` stops early after trying to pass `-v` to `wct`

[mattpalermo]

Description

I cannot run polymer test -v successfully.

Versions & Environment

• Polymer CLI: 0.18.0-pre.15
• node: v6.10.2
• Operating System: Windows 10

Steps to Reproduce

1. Create a polymer 2 application project using polymer init
2. Run polymer test -v

Expected Results

It would execute just as polymer test would except there would be extra information logged to the console.

Actual Results

polymer test -v stopped after trying to call wct with an invalid argument:

C:\Users\Matthew Palermo\dev\PolyList>polymer test -v
debug:   got args:
{ args: [ 'test', '-v' ] }
debug:   got default config from polymer.json file:
{ config: { lint: { rules: [ 'polymer-2' ] } } }
debug:   adding command analyze
debug:   adding command build
debug:   adding command help
debug:   adding command init
debug:   adding command install
debug:   adding command lint
debug:   adding command serve
debug:   adding command test
debug:   running...
debug:   command 'test' found, parsing command args:
{ args: [ '-v' ] }
debug:   command options parsed from args:
{ verbose: true }
debug:   final project configuration generated:
{ lint: { rules: [ 'polymer-2' ] },
  root: 'C:\\Users\\Matthew Palermo\\dev\\PolyList',
  entrypoint: 'C:\\Users\\Matthew Palermo\\dev\\PolyList\\index.html',
  fragments: [],
  extraDependencies: [ 'C:\\Users\\Matthew Palermo\\dev\\PolyList\\bower_components\\webcomponentsjs\\*.js' ],
  sources:
   [ 'C:\\Users\\Matthew Palermo\\dev\\PolyList\\src\\**\\*',
     'C:\\Users\\Matthew Palermo\\dev\\PolyList\\index.html' ],
  allFragments: [ 'C:\\Users\\Matthew Palermo\\dev\\PolyList\\index.html' ] }
debug:   Running command...
'-v' expects a value

Usage: wct [options]

Options:
   -p, --persistent          Keep browsers active (refresh to rerun tests).
   --root                    The root directory to serve tests from.
   --plugin NAME             Plugins that should be loaded.
   --skip-plugin NAME        Configured plugins that should _not_ be loaded.
   --expanded                Log a status line for each test run.
   --verbose                 Turn on debugging output.
   --quiet                   Silence output.
   --simpleOutput            Avoid fancy terminal output.
   --skip-update-check       Don't check for updates.
   --webserver-port          A port to use for the test webserver.
   --color
   --compile                 Whether to compile ES2015 down to ES5. Options: "always", "never", "auto". Auto means that we will selectively compile based on the requesting user agent.

   -l NAME, --local NAME     Local browsers to run tests on, or 'all'.
   --selenium-arg ARG        Additional selenium server arguments. Port is auto-selected.
   --skip-selenium-install   Skip trying to install selenium.

   -s NAME, --sauce NAME     Remote Sauce Labs browsers to run tests on, or 'default'.
   --sauce-username          Sauce Labs username.
   --sauce-access-key        Sauce Labs access key.
   --sauce-tunnel-id         Sauce Connect tunnel identifier.
   --build-number            The build number tested by this test for the sauce labs REST API.
   --job-name                Job name for the sauce labs REST API.
   --visibility              Set job visibility to 'public', 'public restricted', 'share', 'team' or 'private'
   --port                    Select an alternative port for Sauce Connect (default is 4445)

[mattpalermo]

Ah, I found that polymer test --verbose works.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.