| Subject: | prove -v and no_plan give bad TAP output |
For this test file:
use Test::More qw(no_plan);
ok 1, "wrong line";
With Perl alone:
wallflower 11:57:59 ~ $ perl sample.t
ok 1 - wrong line
1..1
(This is correct; ok 1 comes on its own line)
With prove -v:
wallflower 11:58:11 ~ $ prove -v sample.t
sample....ok 1 - wrong line
1..1
ok
All tests successful.
Files=1, Tests=1, 0 wallclock secs ( 0.04 cusr + 0.00 csys = 0.04 CPU)
(First 'ok' line is on the wrong line.)
This makes it difficult for a Straps-based TAP post-processor to read the TAP output and get it right. (Why am I processing it twice? Historical reasons.)