On 22 Sep 2006, at 15:43, Ovid wrote:
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):
[snip]
# 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.
[snip]
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.
Something like this might actually be a nice way to kick start some
experimentation with TAP2.0 type thangs - since you seem to have the
spare time to code at the moment :-)
(although, in this particular instance I question whether you need
separate prefixes for TODO output and diagnostic output - wouldn't
the preceding test give us the info to differentiate the two?)
Adrian
