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.

Massive TAPx::Parser regression tests 5 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Test::Harness uses the exit status of a test script.

    —Theory

    • Yes, but it's apparently to represent the number of failed tests and that caps out at 255, so you can't even report the number of failed tests correctly unless it's less than that magic number. VMS doesn't even get that right, so the exit status doesn't seem terribly useful. On the Perl-QA list, chromatic suggested that I just ignore it. However, if someone is actually using it, I'll need to know how and why.

      Plus, this is part of a project to replace Test::Harness and its limitations. This appears to be another one, but I'm not sure.

      Oh, and I'm up to 717 regression tests now, bringing me to 1177 total :)

      • I don't see why you don't validate that the exit status is zero. Your programs never segfault or die without ever printing useful information?

        Or maybe the thing runs all the way through and segfaults in an END block. Maybe the official part of the test is already over but you can notice that the test still died a bad death.

        • Yes, that's what I meant, though that's certainly not what I wrote to perl-qa. An exit status of zero or not-zero is useful information. Anything else seems somewhat useless.

          • Absolutely. It's not like we're dealing with sendmail, where it does need to deal with the different varieties of code in sysexits.h.

            -Dom

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