You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to spit out a TAP so that I can get machine-generated reports and stuff, but AVA's built-in reporter is way more human-readable than any of the existing TAP parsers (also, TAP seems to be nearly a dead format with most parsers having no changes in the last 8 years). I'd love to have a flag --tap ava-results.tap which would tee the results in TAP format while still emitting from the default reporter. The current behavior of --tap without any flag could still replace the default reporter, as could --tap -.
The text was updated successfully, but these errors were encountered:
I'd love to expose AVA's richer internal data and have separate reporters that can be piped into, but that's unlikely to get done any time soon.
Even with that approach, teeing the richer data to a file would still be useful, so I'm not opposed to establishing that feature with the current TAP reporter.
Hopefully the internals allow for two simultaneous reporters to be active!
I'd love to expose AVA's richer internal data and have separate reporters that can be piped into, but that's unlikely to get done any time soon.
Might I suggest (and I know this is a bunch of extra work) trying to get together with a couple of other test runner maintainers to come up with a standard format
I want to spit out a TAP so that I can get machine-generated reports and stuff, but AVA's built-in reporter is way more human-readable than any of the existing TAP parsers (also, TAP seems to be nearly a dead format with most parsers having no changes in the last 8 years). I'd love to have a flag
--tap ava-results.tap
which would tee the results in TAP format while still emitting from the default reporter. The current behavior of--tap
without any flag could still replace the default reporter, as could--tap -
.The text was updated successfully, but these errors were encountered: