One simple way I used for a project had a special script that knew about test ordering as well as group ordering. Basically, this was set up in the __DATA__ section of the test script something like...
#testname testgroup
base.t core
dvd_core.t core
dvd_mount.t dvdread
dvd_read.t dvdread
dvd_burn.t dvdwrite
tape_core.t core
tape_mount.t taperead
tape_read.t taperead
tape_write.t tapewrite
This described the test order (from top to bottom) and the test group name.
The user would invoke the script like "test.pl taperead" (or via make) which would run the non-hardware tests ("core") and then test mounting and reading (but not writing) a tape. That way I could just run the tests I wanted (some were very time consuming) and I didn't have to put checks in the various scripts for hardware existence and mess with embedding Test::More SKIP sections everywhere. Obviously you can get sophisticated here wrt groupings, but it's pretty easy to set up a basic group dependency list with a hash.
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.