Add a --file <filename> option for json-cov, json and html-cov reporters

[hostalerye]

This option allows the user to write the report in a file

[tj]

why not just redirect stdio?

[hostalerye]

Actually I work with nherment, so that's for the same reasons he mentioned on this topic: #304 (comment)

[VitalyDov]

Hi,

We working on big project uses Express and Mocha as testing framework.
For our integration in Jenkins, we need doc and xunit reporters output to files (just mocha output!)
Do you have any plan to provide such functionality?
Thanks a lot!

[anacronw]

You can cat the head and tail bits. Mocha's documentation is supposedly generated with this (from the "doc" documentation: http://visionmedia.github.com/mocha ):

test-docs:
make test REPORTER=doc
| cat docs/head.html - docs/tail.html
> docs/test.html

[VitalyDov]

Hi badunk,
Thank for your quick answer!
Do you have some solution for xunit? (we really need it for Jenkins)
Thanks!

[anacronw]

I just did a search and this came up: #83

[VitalyDov]

Hi badunk,
Yes, I saw this solution, but it not solve the problem :(
The problem, that redirected output file (tap, xml ... ) contains both mocha output and also output from other modules in shuffle manner.We don't want to parse this file for extract only Mocha's messages in order that Jenkins can take it.
Thanks again.

[VitalyDov]

Hi badunk,
Any news regarding this issue?
Thanks.

[anacronw]

I have not tried any of those solutions myself, all I did was read documentation :) I don't know if commenting back and forth on this pull request is the best place to get your answer.

If this is a blocker for you, I suppose you can try hostalerye's pull request.

[VitalyDov]

Ok, thanks

[blmarket]

+1 for supporting file options to html-cov, because I'm writing some testcases which makes HTTP request to my developing services, and these services can't give me coverage results. I wrote my own coverage-write function, but mocha's reporter doesn't support arbitrary filenames...

[evadnoob]

https://npmjs.org/package/xunit-file Seems to work well, generates a file called xunit.xml seems good enough for now. The need for this is real, since tests may produce useful logging, and expecting the only output from tests to be xml is overly simplistic.

[beaugunderson]

I think it would still be useful to provide the file name parameter that's in this pull request because some node modules also emit their own messages to stdout (and don't provide a method to disable them). This is the hack I settled on to get my coverage JSON:

mocha -R json-cov $FILE | perl -0777 -pe "s/(?s).*?{\n/{\n/" > $FILE-coverage.json

[mkotsbak]

Why are you not merging this? It is very annoying for using Jenkins with output like this:

Express server "undefined" listening on port 8000 in development mode

Then Jenkins complains: Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.
at org.dom4j.io.SAXReader.read(SAXReader.java:482)

[guillaume86]

+1 I have some modules output before the html when piping stdio ...

[balnagy]

This feature would be useful in Grunt environment. Now I have to do in this way with exec plugin, but with this feature I could use the proper mochaTest with file option.

exec: {
 coverage: {
  command: 'mocha -R html-cov ./test/**/*.js > /tmp/coverage.html && open /tmp/coverage.html',
  stout: true
 }
},