Hi all,
So here's the thought. If we accept that TAPx::Parser might override certain
bits of Test::Builder's behavior, what about the following *completely optional
behavior that you must explicitly request from TAPx::Parser* (borrowing from
earlier suggestions):
use Test::More qw/no_plan/;
diag 'Wibble!';
TODO: {
local $TODO ='gnarflebitz';
is 23, 42, 'whee!';
}
ok 1;
is 'this', 'that', 'aw, shucks';
Outputs:
# Wibble!
not ok 1 - whee! # TODO gnarflebitz
#! Failed (TODO) test 'whee!'
#! in builder.t at line 6.
#! got: '23'
#! expected: '42'
ok 2
not ok 3 - aw, shucks
#> Failed test 'aw, shucks'
#> in builder.t at line 10.
#> got: 'this'
#> expected: 'that'
1..3
# Looks like you failed 1 test of 3.
It's valid TAP and, as a temporary hack, I can then use this:
my %leader = (
'# ' => 'comment',
'#!' => 'todo',
'#>' => 'diagnostic',
);
It's not great, but it's unambiguous, it doesn't break anything. It's only
used if people explicitly ask for it AND it guarantees that you can parse the
comments reliably and do useful things with them. I think it would be a great
stop-gap measure until TAP 2.0 is sorted out.
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
