I would just like to say that redundant tests have some negative qualities:
- The test suite will run slower, and with 2,500 tests, that is going to become an issue.
- Time spent developing unnecessary tests detracts from development of new code.
I have some common sense guidelines for test writing:
- Test the boundary cases far more than the regular cases.
- Focus tests on buggy or expected-to-be-buggy code.
- If you can write the test cases first, then good for you, but be aware that the test suite is broken until the code is completed.
- Interesting things happen when Person A writes tests for Person B's code.
- If you have performance requirements, write tests that only pass if those requirements are met.
- Coverage is important.
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:
- 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
Outside of code tags, you may need to use entities for some characters:
| |
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.
|
|
