There are a few CPAN modules that have
excessive testing time when being installed (or reinstalled). Hint: if it takes more than a minute or two, I'm likely to be irritated.
In class today, it occurred to me that these tests could be conditional upon the presence or absence of an environment variable:
use Test::More tests => 120;
...
SKIP: {
skip "skipping really long tests", 95 unless $ENV{ALL_TESTS};
... 95 tests here ...
}
That way, the developer can capture the full test suite for development and maintenance (
make test ALL_TESTS=1), but as an installer, I don't have to sit through the whole thing, and I can know just how little I can get away with for a first-order "ok to install" test.
Please consider this if you're a module author. Be kind to your remote installer person.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
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.