-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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? #1326
Comments
👍 very much so. I'll catch up with the discussion thus far this weekend, and add my views. Great initiative! |
i f*cking love open source. |
@JamesMGreene This is brilliant. My only concern is losing functionality. If framework passes data x to its reporters, how can we ensure that x will appear in the universal reporter? I'm curious where the framework would end and the reporter would begin. Would the framework interface with some sort of common adapter, or the reporters themselves? Please create a new repo and/or org for this initiative so we can centralize the discussion? Excited about this! |
Will do. |
Anyone from "Team Mocha" who wants to join in on this discussion, please let me know. For now, I've added @visionmedia, @boneskull, @jbnicolai. |
@JamesMGreene please add @travisjeffery thanks! |
TJ can still be an honorary member if he likes. 😜 Added @travisjeffery. |
closing as discussion has moved to js-reporters |
👍 |
Hi, I would like contributing to https://github.com/js-reporters/js-reporters in anyway I can. Can anyone help me, from where I can start? I have already built the repository and fairly gone through the code base. |
@Dinuka2013513 there's several open issues that you could help with: https://github.com/js-reporters/js-reporters/issues You could also help finish the mocha adapter: qunitjs/js-reporters#28 |
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?
Cross-reference issues:
cc: @jzaefferer @Krinkle @leobalter
The text was updated successfully, but these errors were encountered: