I test as much as I can, for two reasons:
- I have found the weirdest stuff break, stuff I would never have imagined.
- It's a form of documentation, for those of us without documentation sections in our non-existent project plans.
The only warning I'd have is that whenever a test fails, you have to make sure it's testing what you want it to. Recently, I made a necessary non-backwards-compatible interface change. Worked fine. Then, I started using it. Made a few more changes, then BAM! a test started failing. I looked deeper and found it was a test I hadn't updated when I made my interface change. The test hadn't been testing what I thought it had.
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||