Skip to content
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

Support mocha reporters #3

Closed
jb55 opened this issue Jun 11, 2014 · 6 comments
Closed

Support mocha reporters #3

jb55 opened this issue Jun 11, 2014 · 6 comments

Comments

@jb55
Copy link
Contributor

jb55 commented Jun 11, 2014

I'm not a mocha expert but I imagine you would need mocha to run multiple reporters? json-stream for persistence and another reporter of your choice. Is there any way to do this without running mocha twice?

@juliangruber
Copy link
Contributor

@visionmedia suggested inheriting / overriding mocha's lib/runner.js
Another idea would be to always use json-stream and have some code that takes mocha's reporters and applies them to that

@tj
Copy link

tj commented Jun 11, 2014

seems like an odd place to report this haha but we already have a mocha issue for multiple reports via some standard json stream thingy

@jb55
Copy link
Contributor Author

jb55 commented Jun 11, 2014

Ah yeah, looks like mochajs/mocha#492 is what would make this easier

@tj tj closed this as completed Jun 11, 2014
@jb55
Copy link
Contributor Author

jb55 commented Jun 12, 2014

I just put together mocha-report so you can do this now:

$ mocha-broken | mocha-report spec

@juliangruber
Copy link
Contributor

awesome! do you want to make a PR to add this to mocha-broken?

@jb55
Copy link
Contributor Author

jb55 commented Jun 12, 2014

Sure I just need to put together a slightly modified json-stream reporter that has error messages and then I'll make a PR

On Wed, Jun 11, 2014 at 9:31 PM, Julian Gruber notifications@github.com
wrote:

awesome! do you want to make a PR to add this to mocha-broken?

Reply to this email directly or view it on GitHub:
#3 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants