I'm on the edge of this whole unit test thing. It's not that unit tests are bad, they aren't, but for certain applications ... say systems monitoring and GUI apps (not always Perl), it's incredibly hard to write good unit tests. Small code (i.e. modules) can have unit tests pretty easily, large apps can be a challenge.
Furthermore, unit tests can help find problems, but fully successful unit tests can lead to false positives. You still can't test to see if your code will seg fault on RH QU 3 ... no matter what you do.
Meanwhile, if you are only unit testing your external API's, yes those API's shouldn't break when refactoring things. But if you are testing internal API's, well, it's ok to break those!
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.