Re: Parsing TAP into TAP

* Andy Armstrong [EMAIL PROTECTED] [2007-12-10T11:52:33] On 10 Dec 2007, at 16:49, Ovid wrote: Seems Ricardo Signes likes this idea, too: http://use.perl.org/~Ovid/journal/35076 Who? :) :'( I like this idea so much that if you point me at a repo and failing tests, I will try to be a

Parsing TAP into TAP

Test results currently look something like this: t/foo.t. ok t/bar.t. ok t/baz.t. 23/? # Failed test at t/baz.t line 9 # Looks like you failed 2 tests out of 23 t/baz.t. Dubious, test ... Why do we do this instead of

Re: Parsing TAP into TAP

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

Re: Parsing TAP into TAP

--- Andy Armstrong [EMAIL PROTECTED] wrote: 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.

Re: Parsing TAP into TAP

--- Andy Armstrong [EMAIL PROTECTED] wrote: 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 Seems Ricardo Signes likes this idea, too: http://use.perl.org/~Ovid/journal/35076 Cheers, Ovid -- Buy the book -

Re: Parsing TAP into TAP

On 10 Dec 2007, at 16:41, Ovid wrote: It's actually quite easy to do - just need to plug in a different formatter. Plan == number of test files etc. Regrettably, this is merely a gut feeling of mine. Think of the 'Result: PASS' we have at the end of our output now. That could go away.

Re: Parsing TAP into TAP

On 10 Dec 2007, at 16:49, Ovid wrote: 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 Seems Ricardo Signes likes this idea, too: http://use.perl.org/~Ovid/journal/35076 Who? :) Well, let's do it. Blocks and all. --

Re: Parsing TAP into TAP

Ovid wrote: Test results currently look something like this: t/foo.t. ok t/bar.t. ok t/baz.t. 23/? # Failed test at t/baz.t line 9 # Looks like you failed 2 tests out of 23 t/baz.t. Dubious, test ... Why do