Since, if you look at the output when
make test is run, all files in
module/t. are run in directory listing order, why not take advantage of that - as I and a good number of others do. This is done by prefixing the test files (i.e.
t/*.t) with a number e.g.
t/00_base.t
t/01_base+1.t
.
.
etc. etc. - or in your case
t/00_perf1.t
t/01_perf1.t
t/02_perf2.t
.
.
/C>
or maybe even more meaningful names (to you) than <c>nn_perfnn.t
You will undoubtedly find perl testing - A developers notebook to be of great use (it's where I had the above idea confirmed by far more knowledgeable others).
Update:
Added afterthought/post-script ... which should have been the first thought!!
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.