There are two distinct things that you need to test: first, the ability to connect to a database of the expected type; second, the ability to interact with the database and to demonstrate that the correct set of changes are applied to it. The latter situation, I think, is likely to be “particular to the (usually...) known target type of database” that I personally would be less than willing to substitute another one. Normally, I set up a testing-only database that is used only for automated tests, and the first step of that script is to run an external command that first drops and then reloads the database with known initial content. Sometimes that script is re-run several times. (In one commercial situation, we set up the first test to run an md5sum against the source-data script itself to guard against innocent but undocumented out-of-process changes to its “known” content.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
