You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I attempt to use a built in reporter such as dot or xunit, it works fine. But If I attempt to use a third party reporter such as xunit-file or mocha-teamcity-reporter, then I get this error:
I saw in a IRC log someone mentioning that this error occurs when the reporter runs in nodejs instead of phantomjs. I'n not sure how to fix it.
I'm working this around by using the xunit reporter and directing the console output to a file, then having teamcity process that result file. But then I cannot print any messages during my tests (else the XML in that redirected file gets corrupted).
The easiest way to repro is to have node on Windows (I'mm on Windows 8.1), then install xunit-file reporter and try using it.
The text was updated successfully, but these errors were encountered:
You got it backwards, but yes - the reporters run in PhantomJS, not Node.js, as noted in the readme. path is a Node.js specific module so it will not run in PhantomJS or the browser for mocha-phantomjs.
I see alot of issues regaurding xunit reporter on mocha-phantomjs, like nathanboktae/mocha-phantomjs#161 - see if those help you. Basically the xunit reporter just needs to use vanilla javascript to run, or depend on a XML module that it and all it's dependencies don't need node or browser specifics (big ask I know).
When I attempt to use a built in reporter such as dot or xunit, it works fine. But If I attempt to use a third party reporter such as xunit-file or mocha-teamcity-reporter, then I get this error:
I saw in a IRC log someone mentioning that this error occurs when the reporter runs in nodejs instead of phantomjs. I'n not sure how to fix it.
I'm working this around by using the xunit reporter and directing the console output to a file, then having teamcity process that result file. But then I cannot print any messages during my tests (else the XML in that redirected file gets corrupted).
The easiest way to repro is to have node on Windows (I'mm on Windows 8.1), then install xunit-file reporter and try using it.
The text was updated successfully, but these errors were encountered: