Share a standard Reporter interface?

[JamesMGreene]

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:

• Standard reporter interface qunitjs/qunit#531 (original discussion)
• Share a standard Reporter interface? mochajs/mocha#1326
• Share a standard Reporter interface? theintern/intern#257

cc: @jzaefferer @Krinkle @leobalter

[boneskull]

(please say yes)

[ragaskar]

I'm not philosophically opposed, as long as we're talking about a base minimum API, so that Jasmine might be able to have a superset if necessary. I can imagine this taking a bit of time, particularly if there is data that we don't currently track and don't really have access to that becomes part of the standard. Seems like a win for most people though.

There are a few Jasmine guiding principles that could come into conflict (avoid external dependencies, avoid DOM/Browser binding where possible): essentially we'd want to see the format be implementable in plain javascript.

@infews, @sheelc, @jboyens, @Gerg, @tjarratt: thoughts?

[JamesMGreene]

Anyone from "Team Jasmine" who wants to join in on this discussion, please let me know. For now, I've added @ragaskar, @infews, @sheelc, @jboyens, @Gerg, @tjarratt.

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

[JamesMGreene]

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

[slackersoft]

Can you add me over there as well? Thanks.

[JamesMGreene]

Done @slackersoft.

[slackersoft]

Closing this issue in favor of keeping the discussion in the js-reporters group