The main problem (in my particular case) is that single test cases are slow (taking up to one or two seconds on my slow machine). Splitting the test file into smaller chunks (How many tests per file? 30? 20? 10?) would still leave me the problem that it could take 10 seconds or more to actually run the faulty test --- to long for development.

And for the "too complicated" argument: the failure of a test is a unusual thing, and normally only I will see the failure and very probably it's also just me who will debug and handle the error. A solution which works for me is absolutely OK. I don't need a "nice" solution, just a working solution.

In reply to Re^5: How to test less with Test::More? by eserte
in thread How to test less with Test::More? by johnnywang

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.