Implement support for multiple reporters

[benvinegar]

Continuation of #1681, targeted against 2.x (master) instead of 3.x.

Necessary for completion:

• support distinct output streams for each reporter (e.g. 'spec' → stdout while 'json' → file)
• --reporter-options needs to be capable of configuring each reporter

[boneskull]

fyi: with the linting work that's being done, we're not going to be using leading commas. also, the below conditional will need curlies

[benvinegar]

Roger.

[boneskull]

@benvinegar

support distinct output streams for each reporter (e.g. 'spec' → stdout while 'json' → file)

Is this in-progress or...?

[danielstjules]

@benvinegar Awesome work on this btw :)

Is this in-progress or...?

@boneskull It might be difficult without a writeable stream being passed to each reporter, since they all invoke either process.stdout.write or console.log directly. Ideally, mocha would pass process.stdout to any reporter writing to stdout, and an fs.WriteStream when writing to a file (or just some buffer that gets written at the end of exec). At that point you'd probably end up with something similar to what you mentioned in #1772 (comment)

@benvinegar Did you have an easier solution in mind for getting the distinct output streams working? I've got some cycles this week too if you wanna collaborate.

[atticoos]

This would be great to have :)

[lostthetrail]

This is a super useful feature. It appears the development has stalled on it?

[benvinegar]

This is stalled. Sorry everyone. Ultimately I was driven on this project because it was important for a project I was working on, but I've since moved on and it's no longer in my sights. The small handful of comments over the past 6 months hasn't really motivated me sufficiently to continue.

@danielstjules – This is a super late reply, but if we could get together to push through on this, I'm game.

Otherwise I can help someone else take over.

[antoinebrault]

+1 really need this for CI.

[lpinca]

I would also love to have this for the same reason mentioned by @antoinebrault.

[boneskull]

Anyway, a prototype of #1969 will have this built in

[machineghost]

Please, someone finish merging this; having to run your entire suite multiple times just to get xunit and coverage reports is lame.

[boneskull]

@antoinebrault @machineghost @lpinca you may want to take this PR over and see if you can get it finished. my focus is elsewhere atm

[santiagoaguiar]

@boneskull @benvinegar I'll be integrating the current work on latest and add the missing pieces, any things to keep in mind?

I'm working over master, should I do it on 3.0 instead?

[santiagoaguiar]

First question: most of the reporters in mocha do a direct process.stdout.write or console.log, but to ensure they can be used while passing --reporter reporter:outputfilename they should instead use the inherited write method from the Base reporter that was added on this PR, which does a process.stdout.write (which, by the way, should probably fallback to console.log for browser environments?). I guess this is what was being discussed on #1772 (comment).

Any reason not to do such change?.

Since this requires updating every reporter, I'm guessing we should do that on an independent PR?.

[benvinegar]

See #2184