Hmmm ,
I can't speak for the module author, but I'd second guess that the purpose behind some specified plan i.e. a possible answer to your 1st question, is to give yourself (and Test::More) some level of confidence that you thought things thro' prior to implementing the tests.
Moreover, I'd refer you to Perl Testing - A Developers Notebook.
Personally, I've found it [specifying the expected number of tests] useful on 3 counts:
- It gives me a higher degree of confidence that I know what's going to be tested and have planned accordingly.
- Twice now I've planned to run n tests, only to find m have been run instead and thus (when run with TEST_VERBOSE=1) I was, in both cases, able to identify the errant test(s) and correct the situation (by fixing the bug that prevented their execution ... c/w adjusting the number of test to be run, of course:-))).
- Finally, as a metric - to keep management 'happy'.
A user level that continues to overstate my experience :-))
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.