Participate in discussion about a shared/common Reporter interface?
JamesMGreene opened this issue · comments
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.
- an EventEmitter interface (
- 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:
Did anything ever come of this? Closing for now, but happy to reopen if there's some kind of standard to adhere to.
@ljharb The spec is taking shape. I've sent you an invite to the org and chat room. Would love to get this to the next level!
Closing for now; happy to keep participating in js-reporters efforts if they resume.