If there are holes in your test scripts, then they are not testing everything you deem important! If you can't trust your test suite to test your scripts and modules, then what can you trust? A hit-and-miss perl -c
approach will be unlikely to pick up any more bugs than your tests. If you don't think your tests are good enough, I'd get intimate with the relevant incompatible changes in the perldelta
s (a quick search on your scripts for threads and unicode might not go amiss); then install your modules and scripts on a dev box, and run them into the ground with automated tests
. Whenever you find a bug, add it to the test suite, and that's one less thing you need to do manually next time. Best of luck with it.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||