Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

  (email not shown publicly)
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Saturday April 05, 2008
04:47 AM

Oslo: TAP Diagnostics

[ #36065 ]

Sitting in Oslo right now. We are now nailing down the new YAML diagnostic syntax. Tentatively we have something like this:

TAP version 14
   ok 1 - Input file opened
   not ok 2 - First line of the input valid
       have: 'Flirble'
       want: 'Fnible'
     severity: fail
     file: t/foo.t
     line: 12
       - IO
       - config
     source: is $line[0], 'Fnible', 'First line of the input valid';

There are other keys like 'timestamp', url', 'display' and similar that will likely be included. All are optional.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Please make sure to specify that the diagnostics have to conform to the YAML Tiny [] subset of YAML.

    • Why? Do recall that this is also be allowed for other languages with different data structures with different serialization requirements.

      • Precisely. YAML is not suitable for high-fidelity serialisation. You really want eg. Data::Dump::Streamer if your data structures are tricky.

        However, writing a YAML parser is a much bigger job than writing a TAP parser. Parsing YAML Tiny is on par with parsing TAP, and the dialect is perfectly sufficient for modest serialisation needs.

        So demanding a full YAML parser to parse TAP won’t provide substantial benefit but may hamper adoption of TAP.