I have very similar logic in a number of my test scripts. I use an eval block and check that the message in $@ matches what I was expecting. That won't work directly for you since your code uses 'carp' where mine uses 'croak'.

If one of your methods is passed an invalid argument, is there any point carrying on? Rather than carp and return 0, why not just croak?

Coming back to your original question though, you could capture warning messages like this:

  our $last_warning = '';
  $SIG{__WARN__} = sub { $last_warning = shift; }

  ... code that generates warning ...
  ... code that checks contents of $last_warning ...

[download]

In reply to Re: Silencing warnings when testing by grantm
in thread Silencing warnings when testing by astaines

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.