These diagnostic keywords seem to blend too much into the rest of TAP. Consider:
not ok 2 - omg t3h sooper test!!1! ! file: foo.t ! line: 45 ! description: omg t3h sooper test!!1! ! got: this ! expected: that ! raw-test: is( "this", "that", "omg t3h sooper test!!1!" ); ! x-THAC0: 16 ...or some other delimiter. Or maybe we say that any inline YAML is interpreted as a comment data structure instead of a giant comment string, which can be used for diagnostics: not ok 2 - omg t3h sooper test!!1! --- TAP diagnostics file: foo.t line: 45 description: omg t3h sooper test!!1! got: this expected: that raw-test: is( "this", "that", "omg t3h sooper test!!1!" ); x-THAC0: 16 ... On 7/10/06, Michael G Schwern <[EMAIL PROTECTED]> wrote:
The PITA/TestBuilder2 BoF at YAPC::NA (which spent most of its time talking about TAP) sketched out a syntax for parsable TAP diagnostics. not ok 2 - omg t3h sooper test!!1! file: foo.t line: 45 description: omg t3h sooper test!!1! got: this expected: that raw-test: is( "this", "that", "omg t3h sooper test!!1!" ); x-THAC0: 16 Details on the wiki. http://perl-qa.yi.org/index.php/TAP_diagnostic_syntax
-- Ian Langworth
