Once you've caught the testing bug, you can take things to the 'next level' by releasing your code to CPAN. Then the CPAN Testers team will introduce you to the joys of cross platform testing issues.
I've learnt numerous lessons the hard way (many of which in retrospect were pretty bloody obvious), including:
- don't assemble pathnames using '/' - use File::Spec
- don't assume everyone has a recent version of Perl
- be careful that your tests don't make any assumptions about the order of keys in a hash
- don't assume any relationship between the current system time and the timestamp on that file you just created (the fileserver time may be different)
- make sure you know which version of other modules you depend on - you don't want their old bugs to break your test suite
- don't assume anyone will read the README - try to integrate all dependency checking into your build process (ie: before the tests run)
- just because a module you require is installed don't assume it works (there are a surprising number of people who watch 100% of tests fail, run make install anway and congratulate themselves on a job well done)
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||