comment on

I don' t know where it falls in skill or teaching target but I strongly prefer the done_testing($n) idiom. The main reason is it lends itself to flexibility and a bit of intention documentation in growing/maintaining tests, for example cases like this–

my %tests = ( case1 => { input => …, output => … },
              case2 => { … } );

subtest "Something" => sub {
    plan skip_all => "Moon is not full" unless …;
    ok 1;
    ok 2;
    done_testing(2);
};

for my $test ( values %tests )
{
    ok $test->{input}, "Have input…";
    is process($test->{input}), $test->{output}, "Process works";
}

done_testing( 1 + 2 * keys %tests );
[download]

In reply to Re^3: RFC: Basic Testing Tutorial by Your Mother
in thread RFC: Basic Testing Tutorial by hippo

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 How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks