You might consider using Test::Class which is great for organizing your test suite into libraries. In your test module, you then define a subroutine which runs the tests and pass it the number of tests. That way, you don't really need to know the total number of tests, just the number of tests in a subroutine which ideally would test a particular feature or portion of your code base.
package MyTestModule; use base qw/ Test::Class /; use Test::More; sub test_sub1 : Test(2) { my $self = shift; ok(....); ok(....) }
When you update the test_sub1 subroutine to include or remove a test, just change the number in the attribute to the sub. Very convenient! You can also do this.
sub test_sub2 : Test(no_plan) { my $self = shift; ... ... }

--
Rohan


In reply to Re: Counting test cases by arc_of_descent
in thread Counting test cases by kyle

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.