On 10 Dec 2007, at 14:17, Ovid wrote:
And we could even add diagnostics for the non-failing tests. This
could be an alternate output, but now instead of external tools having
to try and parse our ad-hoc Test::Harness output, we could have an
alternate machine read-able output that those tools could use. Now if
only we had a useful way to read that output ...
I like it. But I can't think of a use case off the top of my head. So
are you thinking something like
$ prove --tap
?
It's actually quite easy to do - just need to plug in a different
formatter. Plan == number of test files etc.
--
Andy Armstrong, Hexten
