Share a common Reporter interface?

[JamesMGreene]

We on the QUnit team have been discussing the possibility of working with other JS test frameworks, especially those that can be run client-side (e.g. Mocha, Jasmine, Intern, Buster, etc.), to agree upon a common Reporter interface so that we could hopefully share Reporter plugins between testing frameworks.

This would most likely come in the form of:

• a common Reporter API/Interface, e.g.
  • an EventEmitter interface (.on(...)/.off(...)) OR an object with standard "hook" properties
  • maybe a standard-ish way to register a Reporter, e.g. MyLib.addReporter(x), MyLib.reporter = x;, etc.
• a minimum viable set of standardly-named events
  • an associated standard set of data/details provided for each event
• a minimum viable set of standard test status types (e.g. pass, fail, skip, todo, pending, etc.)
• updating all participating test frameworks to support this new common Reporter interface

Would you guys be interested in discussing this further with us? If so, please let me know who I should invite to participate.

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

Cross-reference issues:

• Standard reporter interface qunitjs/qunit#531 (original discussion)
• Share a standard Reporter interface? mochajs/mocha#1326
• Share a standard Reporter interface? jasmine/jasmine#659
• Share a standard Reporter interface? theintern/intern#257
• Share a standard Reporter interface? busterjs/buster#419
• Share a common Reporter interface? caolan/nodeunit#276

[indexzero]

I love this idea

[JamesMGreene]

@indexzero: Would you like to be invited, then? Anyone else from the Vows team I should invite?

[indexzero]

Yes. Invite @JerrySievert and @davglass

[JerrySievert]

i would love a common reporter interface. been struggling with some non-common ones as i have moved between testing frameworks to conform to other environments (hapi, gulp, etc). this would make my, and vow's life better.

[JamesMGreene]

All three of you are now invited. Go to https://github.com/js-reporters to accept the invitation (or via the GitHub email you'll probably receive).

Then please head to https://github.com/js-reporters/js-reporters/issues/ soon-ish as you guys are a bit late arriving to the party (lots of discussion already occurring between QUnit, Jasmine, Mocha, and BusterJS). Thanks!

[JamesMGreene]

P.S. qunitjs/js-reporters#7 ("Roadmap") may be the best place to start as it provides a basic outline of the idea and links to relevant issues for each part.