Is there a better approach to it than that?
I would start by asking myself
what is it I want to test? Write a test strategy, and take it on from there. Then break it down to individual tests e.g.
- Does the application behave as I expect when the database is unavailable?
- Does the application behave as I expect when the database returns unexpected results (e.g. no data, wrong charset, wrong number of columns, wrong data types, ..)?
- Does the application behave as I expect in a foreign environment (e.g. on a different OS)?
- ..
Suggested reading: Perl Testing.
You may also want to take a look at Test::MockDBI (Disclaimer: I one filed a patch to the given module and ended up as its' co-maintainer).
Best of luck.
--
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.