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

Share a standard Reporter interface? #1326

Closed
JamesMGreene opened this issue Aug 29, 2014 · 12 comments
Closed

Share a standard Reporter interface? #1326

JamesMGreene opened this issue Aug 29, 2014 · 12 comments
Labels
type: feature enhancement proposal
Milestone

Comments

@JamesMGreene
Copy link

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

@jbnicolai
Copy link

👍 very much so. I'll catch up with the discussion thus far this weekend, and add my views. Great initiative!

@rosssclafani-zz
Copy link

i f*cking love open source.

@boneskull
Copy link
Contributor

@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!

@boneskull boneskull added this to the v2.0.0 milestone Aug 30, 2014
@JamesMGreene
Copy link
Author

Please create a new repo and/or org for this initiative so we can centralize the discussion?

Will do.

@JamesMGreene
Copy link
Author

Anyone from "Team Mocha" who wants to join in on this discussion, please let me know. For now, I've added @visionmedia, @boneskull, @jbnicolai.

https://github.com/js-reporters/js-reporters

@JamesMGreene
Copy link
Author

@boneskull
Copy link
Contributor

@JamesMGreene please add @travisjeffery
@visionmedia is no longer maintaining the repo

thanks!

@JamesMGreene
Copy link
Author

TJ can still be an honorary member if he likes. 😜

Added @travisjeffery.

@boneskull
Copy link
Contributor

closing as discussion has moved to js-reporters

@JamesMGreene
Copy link
Author

👍

@dinukadesilva
Copy link

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?
Since I'm more familiar with Jasmin and mocha also, I thought of contributing to this.

I have already built the repository and fairly gone through the code base.

@jzaefferer
Copy link

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature enhancement proposal
Projects
None yet
Development

No branches or pull requests

6 participants