TAP support

[sindresorhus]

Should be a flag, like $ ava --tap, to get TAP output. This would be a good way to enable reporters without actually supporting reporters. Can just refer people to all the available TAP reporters instead of reinventing the wheel.

[scottcorgan]

I know that a PR is better than this question, BUT, is this still a priority?

[jprichardson]

👍

[jamestalmage]

From my reading of the TAP spec, I it does not seem very well suited to concurrency. You would need to buffer individual tests and then log them all at once so they don't walk all over each-other.

[vadimdemedes]

Coming Soon!

[vadimdemedes]

TAP support is ready, waiting for #279.

[jprichardson]

After I saw this closed by @vdemedes I assumed it was part of 0.7.0. But didn't see it listed https://github.com/sindresorhus/ava/releases/tag/v0.7.0. Since this issue is still part of 0.7.0, does that mean that it's in 0.7.0 and hence forgotten about in the release announcement or that a new milestone should be associated with this issue?

[jamestalmage]

@jprichardson - We decided to push #279 to the next milestone.

[sindresorhus]

It was closed by a mistake. Planned for 0.8.0.

[jonathanKingston]

@jamestalmage From my reading of the TAP spec, I it does not seem very well suited to concurrency.

That is the case certainly, I am happy to discuss some of my suggestions that have been aired on TAP specification discussions however likely won't be adopted very quickly at all (Having a different output might be simpler)