I'm sort of with others on this. I'd be reluctant to test for file existance, or some of those other things. I think it's better to set/get a test variable when you call it for test mode.
It sounds like this isn't for public consumption (since you mentioned sticking test records in a database). If that's the case, then I'd definitely just have a test variable you can set for unit testing. This may cause you to write some wrapper subs that do the test and return strings based on whether the test was set.
Also, I'd recommend some immediate output (to log or whatever you use) indicating that the module is acting in TEST mode. You really don't want to push that out to prod and end up with test crap in your database.
--
I used to drive a Heisenbergmobile, but everyone I looked at the speedometer, I got lost.
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.