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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I see exactly those problems in large TAP suites all of the time...
    • John had two problems; I am referring to his first:

      Presently, the suite will print out any tests that fail, with their error message – but not print out any of the passed tests (giving you no context to know which particular test failed).

      TAP requires that all test names show up in the output along with result and sequence number. Sure, that doesn’t automatically make it trivial to locate the failing test in a large test suite. But it usually makes it a damn sight easier.

      The other problem – figuring out what the heck it is that the test is testing – is of course something that technology cannot fix. (But it is something that can be improved if the code is written in a language that encourages developer documentation both technologically and culturally – as Perl does with POD. Javascript is handicapped here.)