We need it because we have to report to the overlords how much testing we are doing.

Using the plan in the subtests doesn't work:

$ cat test.t use Test::More; subtest foo => sub { plan_tests => 3; ok 1; ok 2; ok 3; }; $ prove -lrv test.t test.t .. # Subtest: foo ok 1 ok 2 ok 3 1..3 ok 1 - foo # Tests were run but no plan was declared and done_testing() was not s +een. Dubious, test returned 254 (wstat 65024, 0xfe00) All 1 subtests passed
$ cat test.t use Test::More; subtest foo => sub { plan_tests => 3; ok 1; ok 2; ok 3; }; done_testing; $ prove -lrv test.t test.t .. # Subtest: foo ok 1 ok 2 ok 3 1..3 ok 1 - foo 1..1 ok All tests successful. Files=1, Tests=1, ...


The way forward always starts with a minimal test.

In reply to Re^2: Count assertions by 1nickt
in thread Count assertions by 1nickt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.