Participate in discussion about a shared 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

As a likely consumer of such a shared Reporter interface, we suspect you may be interested in participating in the discussions as well. Such a reporter should eliminate the need for any framework-specific shims/plugins/etc. that you may be employing right now to standardize results.

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
• Share a common Reporter interface? vowsjs/vows#313

[Jonahss]

We would definitely be interested in the discussion!

Would be glad to be able to implement the current functionality without having to worry about how reporting is handled differently on different frameworks, thus allowing the easy integration of new or experimental frameworks.

Point of contact would be myself: [email protected] @Jonahss

[axemclion]

+1. I would also like to be involved in this discussion.

[JamesMGreene]

Great! You've both been invited now.