NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
done_testing( $arg )? (Score:1)
I like to use the argument done_testing accepts that lets you say how many tests you expected to have run at that stage.
Its like specifying a plan, except you can do so pro grammatically after the fact, which eliminates the need for tedious manual counting.
All you need to know is how many tests occur within a given block of code and increment your counter respectively.
use Test::More;
my $t;
$t+=2;
foreach ( list() ) {
ok( $_, 'List member ok' );
}
$t+=3; # list called the second time
Re:done_testing( $arg )? (Score:1)
Yes, this seems the way to go to me, especially since I have been writing my tests like
for quite a while now. AFAIC
done_testing($tests)simply removes the need for the uglyBEGINblocks.The other thing I quite like about
done_testingis that is removes the need forSKIP:blocks. Rewriting this (which is generally how I would write a complicated skip block)as simply
seems like an improvement to me. If I think the reason is particularly important I can put in a
skip "reason", 1just to get it recorded in the TAP somewhere.Reply to This
Parent