On 6/25/06, Ian Langworth <[EMAIL PROTECTED]> wrote:
Looks a little familiar.. Great job!
I first wrote it about 2 years ago but only recently decide to
make it available to the general public.
I decided to do so now so it won't come out after the
Big Perl Testing Book you mentioned in here:
ht
On 6/26/06, Leon Brocard <[EMAIL PROTECTED]> wrote:
This is really neat. You might want to add a link to Test::Expect too,
which makes it almost to easy to test terminal-based programs.
I only recently saw Test::Expect, I'll look at it more deeply and
will include a set of examples using it as
hi all :)
so, as a standard practice, I start with
use_ok($class);
as the first test in each file, the idea being that if the class doesn't
compile I shouldn't care about the results of the rest of the test - I
know immediately that subsequent failures are because I introduced a
typo or someth
- Original Message
From: Geoffrey Young <[EMAIL PROTECTED]>
> so, the compile test failed, but bar() could still be called and, in
> fact, even executed successfully.
Hi Geoff,
You've run into a problem which surprises a few folks but definitely causes
problems. In a nutshell, use_ok
Ovid wrote in perl.qa :
>
> You've run into a problem which surprises a few folks but definitely
> causes problems. In a nutshell, use_ok internally traps the "use"
> call with an eval. However, even if it fails (as in your case), the
> bytecode might still be compiled and in memory and, as a res
On 27 Jun 2006 15:01:43 -, Rafael Garcia-Suarez
> my $CLASS;
> BEGIN {
> $CLASS = 'Some::Module';
> use_ok $CLASS or die; # "or die" saves the day
maybe BAIL_OUT could be better than die here, in at least a few cases.
It depends on if you want to stop just this test script
As Test::Expect was just mentioned here, I would like to know why Expect and
thus Test::Expect does NOT work on Windows?
I have also asked this on use.perl:
http://use.perl.org/~gabor/journal/30069
Gabor
