Share a common Reporter interface?

We on the [QUnit](http://qunitjs.com/) team have been [discussing](https://github.com/jquery/qunit/issues/531) 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! :astonished:), 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

从 js-reporters/js-reporters/issues/ 中的集中讨论开始，并审阅链接的 QUnit、Mocha、Jasmine、Intern 和 Buster issues。该 payload 提出了多个相互竞争的接口设计，但没有指定任何 nodeunit 文件、测试、实现负责人或验收标准，因此，具体的下一步首先需要就范围达成一致。

由索引模型根据 Issue 内容生成。