comment on

The main reason I stayed away from Test::Exception was that I didn't want to skip all of the exceptions tests just because it wasn't installed.

Then add it as a prerequisite so it gets installed :-)

That is even more true when I can do much of the same with Error/try

Well you have to type a heck of a lot more by using raw try/catch from Error, as you've seen doing so is prone to error, and you get far less useful messages on test failure.

AND the fact that Error is already a PREREQ for the dist being tested.

If you really don't want to add another prerequisite to the installation, add a local copy of Test::Exception and its dependencies to t/lib and just use it in your test scripts. The module is pure perl.

In reply to Re^2: How not to test exceptions by adrianh
in thread How not to test exceptions by jk2addict

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks