Re: A simple unit test framework
On May 6, 1:27 am, Gianni Mariani <gi3nos...@mariani.ws> wrote:
Pete Becker wrote:
...
Yup. Typical developer-written test: I don't understand testing well
enough to do it right, so I'll do something random and hope to hit a
problem. <g>
I have yet to meet a "test" developer that can beat the monte carlo test
for coverage.
OK - I agree, there are cases where a monte-carlo test will never be
able to test adequately, but as a rule, it is better to have a MC test
than not. I have uncovered more legitimate problems from the MC test
than from carefully crafted tests.
Which proves that you don't have anyone who knows how to write
tests. A carefully crafted test will, by definition, find any
problem that a MC test will find.
In my experience, the main use of MC tests is to detect when
your tests aren't carefully crafted. Just as the main use of
testing is to validate your process---anytime a test reveals an
error, it is a sign that there is a problem in the process, and
that the process needs improvement.
--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34