-
Notifications
You must be signed in to change notification settings - Fork 307
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
Share a standard Reporter interface? #257
Labels
enhancement
A new or improved feature
Milestone
Comments
This was referenced Sep 2, 2014
As mentioned on IRC I’d be happy to see if we can come up with something. @jason0x43 should also be added. |
@jason0x43 has been invited now. |
Reporting for dut... No, I didn't just say that. |
This was referenced Sep 6, 2014
Closed
We’ve introduced a new reporter interface for Intern 3. Unfortunately the js-reporters thing kind of fizzled out, but we can revisit this in the future if anything ends up coming out of that project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We on the QUnit team have been discussing the possibility of working with other JS test frameworks (e.g. Mocha, Jasmine, Intern, etc.) to agree upon a standard Reporter interface so that we could hopefully share Reporter plugins between testing frameworks.
This would most likely come in the form of an EventEmitter interface with an agreed upon minimum viable set of standardly-named events and associated standard set of data/details provided to each.
Would you guys be interested in discussing this further with us?
If so, I've added @csnover to "Team Intern" on https://github.com/js-reporters/js-reporters. Let me know if anyone else should be added.
Centralized Discussions: https://github.com/js-reporters/js-reporters/issues/
Cross-reference issues:
cc: @jzaefferer @Krinkle @leobalter
The text was updated successfully, but these errors were encountered: