I have this idea of putting these tests in another directory so I easily can chose which tests to run

erk. I would just go with an environment variable:

SKIP: {
    skip '$ENV{WANT_HONKING_BIG_TEST} is not set', 1
        unless exists $ENV{WANT_HONKING_BIG_TEST};

    cmp_ok( massive_test, '==', 42, 'blah blah blah' );
}

[download]

You can define the environment variable in your shell startup file, so that you always run the test. Someone who has a passing interest in the module downloads it from CPAN and will not pay the cost of the lengthy tests.

If they encounter a bug and are diligent about it, they'll read the "Reporting bugs" section in your documentation, and learn that there are additional tests that they can run which may help you diagnose the problem more accurately.

I dislike modules that ask "do you want to run these extra tests?". If you have to ask, then you shouldn't run them. People who are in the know and want those extra tests will know how to set up the environment before running CPAN/CPANP in order to get them.

- another intruder with the mooring in the heart of the Perl

In reply to Re: Time consuming tests by grinder
in thread Time consuming tests by jplindstrom

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.