Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

A TAP Parser In 40 Lines of Code 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • What about the return code of the stream? That's YAML, so you'd need a YAML parser. Then there's the whole discussion about the context: what if the status of the test is changed based on the context in which it was run? What if TAP changes? Say you have a TAP emitter which emits V14 and then it spawns another process that emits V15 and your V14 emitter is trying to capture that and nest it. Will the pass/fail rules you have for V14 work for V15?

    I'm still not convinced that having a TAP parser, even a reall

  • Returns codes can be a legitimate concern, but in many cases these are unavailable anyway. Also, context does not change whether or not a test succeeded or failed, it changes the interpretation of whether it succeeded or failed. However, if something fails, it's better to default to failure in the absence of more information.

    As for the v14/v15 issue, if we guarantee that TAP core doesn't change, we're safe. This entire work is designed to eliminate the need to break backwards-compatibility. I think we

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.