I'm contemplating the general problem of how best to classify and organize tests. As a specific example, you might classify and organize your tests like this:

xt/author/pod-coverage.t xt/author/code-coverage.t xt/author/perl-critic.t xt/stress/one-minute-test-run-under-memory-pressure.t xt/stress/one-hour-thread-safety-test.t xt/stress/twenty-four-hour-memory-leak-test.t xt/doco/test-user-doco-1.t xt/rtbug/rt123.t xt/rtbug/rt456.t # ...
An obvious limitation of such a scheme is that a test cannot simultaneously be in two different categories. For example, where should I place an rtbug test that is also a stress test? And a "stress" test may or may not be "long running" - what if I want to run all stress tests, but not the "long running" ones? Arguably, the short running stress tests should be in t/ and not xt/, so that they are run by "make test". Property-like metadata solves this problem, akin to adding "tags" to your photo collection. Tools like prove could be enhanced to allow you to specify boolean combinations of test metadata that you want to run. Maybe what I'm proposing is YAGNI. It seems I'll need to come up with some specific, compelling use cases before I could hope to gain any support for this idea.

Update: Note that the xt/ directory layout recommended by Module::Install::ExtraTests is:

xt/author - run when the tests are being run in an author's working c +opy xt/smoke - run when the dist is being smoked (AUTOMATED_TESTING=1) xt/release - run during "make disttest"


In reply to Re^4: Perl CPAN test metadata by eyepopslikeamosquito
in thread Perl CPAN test metadata by eyepopslikeamosquito

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.