I advocate prevention rather than cure, that is to say, spend sufficient time on code design to limit the complexity of testing and equally to make it a doddle to maintain. In my experience even the most daunting of requirements can and should be reduced to the simplest technical design that does the job.
Or to quote CJ Date: An introduction to database systems, a computer system should reflect the simplest model capable of supporting the data rather than an effort to model the real world.
Update: But, if you've arrived at the end of that road, willingly or not: the most popular standard for a "complete" test set seems to be the set of functionally unique (but may be arbitrarily chosen) permutative cases for each requirement specified for the system.
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.