Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Participate in discussion about a shared/common Reporter interface? #93

Closed
JamesMGreene opened this issue Sep 8, 2014 · 3 comments
Closed

Comments

@JamesMGreene
Copy link

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:

@ljharb
Copy link
Collaborator

ljharb commented Jan 10, 2020

Did anything ever come of this? Closing for now, but happy to reopen if there's some kind of standard to adhere to.

@ljharb ljharb closed this as completed Jan 10, 2020
@Krinkle
Copy link
Contributor

Krinkle commented Sep 24, 2020

@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!

@ljharb
Copy link
Collaborator

ljharb commented Sep 20, 2022

Closing for now; happy to keep participating in js-reporters efforts if they resume.

@ljharb ljharb closed this as completed Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants