Cannot direct a reporter to console out when programatically using protractor about mocha-multi HOT 6 CLOSED

I've never seen that error before, do you know which module is producing it?

Can you get a stack trace, or grep for the phrases in your node_modules folder?

from mocha-multi.

Here's the line that's throwing:
https://github.com/angular/protractor/blob/2.5.1/lib/cli.js#L68

And here's the string it's launcing with (I added some endlines so we can read it here):

Spawn node with arguments: node_modules/grunt-protractor-runner/node_modules/protractor/bin/protractor node_modules/testcore/src/conf/protractor.conf.js 
--seleniumAddress http://localhost:4444/wd/hub --baseUrl https://blahblah.com/ --browser chrome 
--specs workspace/tests/test/e2e/stories/**/*.js 
--verbose 
--mochaOpts.ui bdd 
--mochaOpts.reporter mocha-multi 
--mochaOpts.timeout 540000 
--mochaOpts.reporterOptions.xunit.stdout build-artifacts/reporters/results.xml 
--mochaOpts.reporterOptions.json.stdout build-artifacts/reporters/json-reporter.json 
--mochaOpts.reporterOptions.spec -

It seems to be that last -

So, here's how I fixed it spec: '"-"'
/shrug ?

from mocha-multi.

Nope, take it back. That didn't fix it. It creates a file named "-" and directs spec stdout to it.

from mocha-multi.

Ah, so the problem is that something in the chain is doing an incorrect transformation of those options.

I don't know how protractor expands those arguments, so you'd have to look into how that happens. Perhaps doing arg=val for each one will stop the - getting lost.

from mocha-multi.

I'm not sure what you mean about setting arg=val.

The version of protractor I'm on (2.5) uses the now deprecated optimist for arg parsing. It's also going through the grunt layer, so who knows that's doing to the args as well.

After tinkering with a few more string manipulations I ended up working around it by driving it through the env var.

    process.env.multi = 'spec=- ' 
        + 'xunit=build-artifacts/reporters/results.xml '
        + 'json=build-artifacts/reporters/json-reporter.json';

from mocha-multi.

it might have worked using --mochaOpts.reporterOptions.spec=-, but I forgot you don't get control over how that command string gets created.

Environment variable won't be going away, so should be pretty reliable.

from mocha-multi.