Test::Harness doesn't have control over the signal handlers that the tested code might implement. When you install Class::Does::Everything via cpan or cpanplus, you can't just expect they've written it correctly.

What we could do is have the test programs invoked like this:

  perl -MTest::Harness::SIGDIE t/some_test.t

Then we'd just have to figure out the Test::Harness::SIGDIE magic. Actually, now that I stop to think about it, that might not work either. It still requires the signal handler to be written correctly.

Cheers,
Ovid

New address of my CGI Course.

In reply to Re^2: $SIG{__DIE__} overrides exit status? by Ovid
in thread $SIG{__DIE__} overrides exit status? by Ovid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.