Rather than failing, you could 'skip' the various backend tests (with reason) if they aren't available.

You could also do the same with the whole test script if you haven't been configured got a valid config file.

The skip reason could be a pointer to the README, describing how to configure the tests.

Alternatively, if you do want to access a live db which hasn't been explicitly configured in, then please make sure you use table names which are very likely not to be in use already.

Actually, if you're going the non-configured route, it might be better to abort your test script if your chosen database already exists at start time, to avoid stomping on any data. Then create/drop it during your script(s).


In reply to Re: SQL configurations in automated testing by jbert
in thread SQL configurations in automated testing by skazat

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.