Hello Brethren (and Sisteren!),

I'm going through my first-ever unit testing experience with my first-ever Perl OO module. So far so good, but a couple questions have arisen:

From what I can tell, carp and croak seem to be the way to do "exceptions," correct? (BTW, why the silly names?)

Assuming the above is true, what is the best way to go about testing if something is correctly croaking on invalid input? Should I put the eval blocks right there in the tests, or are there built-in functions that "catch" them? (I couldn't find anything about this in the perldoc testing tutorials or the Q&A here.)

Thanks!

I'm a peripheral visionary... I can see into the future, but just way off to the side.

In reply to Testing my carping by nefigah

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.