On 30/08/07, Ovid <[EMAIL PROTECTED]> wrote: > After doing a bit of thinking about this and chatting with Andy > Armstrong about this, I've realized that much of the current thought > about the TAP diagnostics is wrong. We already have much of what we > want in the TAP line above the diagnostics so there's no need to be > redundant. The "description:" key is gone. > > In fact, there will be no mandatory keys. So for a test like this: > > ok $foo, '... my toe hurts'; > > We might see the following TAP: > > not ok 42 ... my toe hurts > --- > line: 53 > file: t/23-body-parts.t > ... > > But for this: > > is $elbow, $hole_in_the_ground; > > You might get this TAP: > > not ok 12 > --- > line: 15 > file: t/23-body-parts.t > wanted: elbow > found: moron > ... > > Because the current behavior of Test::Harness is to discard "unknown" > lines (except when verbose), you won't even see the YAML.
On a tangent, I think using quotes is important otherwise you end up output like wanted: elbow found: elbow when what you really needed was wanted: 'elbow' found: 'elbow ' I'd even suggest sticking \t and \n in there when required and giving the option of outputting \{x} for unicode characters. The whitespace issue is one I had to deal with when writing Test::Tester as it allows you to check diag strings and they involve plenty of tricky whitespace, F