Re: How not to test exceptions

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. That is even more true when I can do much of the same with Error/try, AND the fact that Error is already a PREREQ for the dist being tested.

Comment on Re: How not to test exceptions

Replies are listed 'Best First'.
Re^2: How not to test exceptions by adrianh (Chancellor) on Jul 23, 2005 at 08:57 UTC
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.	[reply]

Replies are listed 'Best First'.

Re^2: How not to test exceptions
by adrianh (Chancellor) on Jul 23, 2005 at 08:57 UTC

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.

[reply]