Invite other JS unit testing framework teams?

[JamesMGreene]

Are there any other JS unit testing framework teams that we should invite?

• JsUnit: ~4 years stagnate
• JsUnity: ~5 years stagnate
• ScrewUnit: ~4 years stagnate
• JsTestDriver: ~2 years stagnate
• YUITest: Just got axed ~1 week ago

I also think we can safely leave out the server-side-only frameworks like NodeUnit and Vows.

[JamesMGreene]

Maybe BusterJS?

[JamesMGreene]

Invited the BusterJS team: busterjs/buster#419

[JamesMGreene]

@jzaefferer: Do you think it would make sense to include the Karma, BrowserStack, and SauceLabs folks on this effort?

[jzaefferer]

They're all consumers of the reporter interface. I guess they wouldn't care too much about the details and appreciate a standard. Inviting them is probably the best way to find out.

[boneskull]

@JamesMGreene Curious; why leave out the server-side frameworks?

[JamesMGreene]

@boneskull: They were primarily left out as I was wary that we would even succeed among the handful of client-side-capable frameworks but the collaboration is going better than I hoped for so far. I am definitely willing to invite NodeUnit as it already supports custom reporters — and apparently can run in the browser as well! 😲

I'm less sure about inviting Vows but we can at least make the offer.

[JamesMGreene]

Invited:

• NodeUnit: Share a common Reporter interface? caolan/nodeunit#276
• Vows: Share a common Reporter interface? vowsjs/vows#313

[JamesMGreene]

Invited:

• Karma: Participate in discussion about a shared Reporter interface? karma-runner/karma#1183
• BrowserStack: Participate in discussion about a shared Reporter interface? browserstack/browserstack-runner#92
• SauceLabs (unofficial): Participate in discussion about a shared Reporter interface? axemclion/grunt-saucelabs#164

[JamesMGreene]

I think we're covered for now so I'm going to close this issue but feel free to add a comment if you think someone else should join, too.