Yes, if you're testing core functionality. Those tests should be run on every machine. You're going to be the one answering the emails if someone installs something on their machine and there are no tests to catch the machine-specific failure. If a user doesn't want to install those Test::* modules, then they don't have to run make test and they can do it manually.

Where I make exceptions is in t/pod.t and t/pod-coverage.t, because they don't affect the functionality of the code, and won't differ in the results on other platforms than my own. See http://use.perl.org/~petdance/journal/19950 for examples.

Also, anyone reading this may be interested in some of the testing modules listed at http://qa.perl.org/test-modules.html.

xoxo,
Andy

In reply to Re: Should a CPAN module list Test:: modules as dependencies? by petdance
in thread Should a CPAN module list Test:: modules as dependencies? by grinder

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.