To be honest, it works both ways. Avoiding old tests that were passing to see when the new test passes may result in getting the new test passing even though you broke an old previously-working test three hours ago.

I generally try to build up my tests. Early in the test file tests things that later tests require. Testing that I never break fundamentals may not save me much time, but it sure saves me a lot of headache.

Also, I find that the more fundamental the test is, the more isolated it likely is. Things like standalone modules, code that doesn't rely on networking and external devices, that sort of thing. I find my fundamental tests are also usually my fastest, and that peace of mind in ensuring I don't break them is worth the extra couple seconds it takes the tests to run.

In practice, though, I'm usually somewhere in the middle. I put my fundamental tests in the 0[0-9]-* test files, and build up from there. Then, when I'm working on higher-level code, which relies on those low-level fundamentals, in the 5* range or whatever, I'm not usually making changes to the low level code, so I can bypass those by simply running "prove t/5*".

In reply to Re: Order of tests by Tanktalus
in thread Order of tests by davies

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.