Smylers wrote:
>
> Indeed it would be irritating for people to have to install a module
> just so they can test your module. But that's no reason to skip the
> test for those who do have it installed.
>
> Couldn't you put in a conditional test that only executes if require-ing
> Test::Warn succe
Rodent of Unusual Size writes:
> Adrian Howard wrote:
>
> > Test::Warn should do the job:
> >
> > use Test::Warn;
> > warnings_like { carp "Danger! Danger!" } qr/^Danger! Danger!/;
>
> unfortunately, it doesn't appear to be a default part of
> a vanilla 5.6 installation, and i'm loath to requir
Rodent of Unusual Size wrote:
Adrian Howard wrote:
Test::Warn should do the job:
use Test::Warn;
warnings_like { carp "Danger! Danger!" } qr/^Danger! Danger!/;
unfortunately, it doesn't appear to be a default part of
a vanilla 5.6 installation, and i'm loath to require a
module used only during
Adrian Howard wrote:
>
> Test::Warn should do the job:
>
> use Test::Warn;
> warnings_like { carp "Danger! Danger!" } qr/^Danger! Danger!/;
unfortunately, it doesn't appear to be a default part of
a vanilla 5.6 installation, and i'm loath to require a
module used only during installation.
but t
On Tuesday, February 17, 2004, at 03:28 am, Rodent of Unusual Size
wrote:
i want to test error checks in a module i'm working on. the
error paths carp() the problem and then proceed.
is there any way to capture the carp text (without using
some of Carp.pm's internal routines) for testing that t
Title: RE: capturing carp()s in module tests?
> i want to test error checks in a module i'm working on. the
> error paths carp() the problem and then proceed.
>
> is there any way to capture the carp text (without using
> some of Carp.pm's internal routines)
