-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using xunit output with -f option produces empty file #114
Comments
I looked into this - xunit is not populating 'Mocha.process.stdout.write' on the page callback (mocha-phantomjs.coffee, line 73). It does however fire "onConsoleMessage", line 46. I don't have time right now to write up a fix, but I'll look into it in a few days if nothing gets into a pull request. |
I took a look. the The correct fix is to fix that reporter. It would be a trivial PR. |
Grab the next version of mocha that has that fix or use it straight from GitHub |
tons of reporters use console.log including the base reporter. |
What's the use case to dump a bunch of xml to the console window if you're not using something like mocha-phantomjs to get the results out? But yes alot of other reporters use |
@rmthamer Since that PR got reverted, you have two options:
Both of them are good options. |
This still issue is still present |
mochajs/mocha#2005 has landed, so we should be good to re-enable xunit reporter file writing? |
Nothing was ever specifically disabled - it should just work. |
Doesn't this conditional prevent the use of the file argument? https://github.com/nathanboktae/mocha-phantomjs/blob/master/bin/mocha-phantomjs#L122 |
Ah right, I forgot about that :) I'll remove it shortly. |
|
mocha-phantomjs -R xunit -f testfile.xml ./testrunner.html
testfile.xml will show up empty. spec works.
The text was updated successfully, but these errors were encountered: