I would recommend not depending on a fixed set of data, but rather having your tests setup the data they're going to work with, and clean up after themselves. Forcing them to do the setup means you'll be inclined to write your main code such that that's easy, and when you need to change your test data it's right alongside your test code. The cleanup part can be a little trickier, mainly because you may or not want to cleanup when you fail (if you want to inspect the data at the time of failure, you'll want to leave it, but most of the time you won't need it and you'll want it cleaned up for you).

In reply to Re: A Framework for automated DB testing by duckyd
in thread A Framework for automated DB testing by Mutant

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.