Share a common Reporter interface?

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. — and apparently NodeUnit! 😲), 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:

• https://github.com/jquery/qunit/issues/531 (original discussion)
• https://github.com/visionmedia/mocha/issues/1326
• https://github.com/pivotal/jasmine/issues/659
• https://github.com/theintern/intern/issues/257
• https://github.com/busterjs/buster/issues/419

[mreinstein]

I can’t find any mention of assertion counting support in the tap documentation

@dossy I think you’re looking for this: http://www.node-tap.org/api/#tplannumber

[dossy]

FYI, for anyone who stumbles upon this issue in the future, looking for nodeunit support in browserstack-runner, see my PR: Add support for nodeunit. PR#188.