At 08:52 PM 5/12/99, you wrote:
><begin soapbox>
>Suggestion for Metrowerks: Rather than add a feature that hasn't been
>tested, why not wait until its tested then roll it into a release. This
>seems like an obvious bug that should not have slipped by. I don't know
>about anyone else, but I assume if some feature is there then it's been
>tested and known to work. I find items like this to be very frustrating when
>trying to develop a product.
><end soapbox>
A more common approach in the industry is to retest EVERY feature at EVERY
release. This is called regression testing. It is apparent that Metrowerks
has not yet adopted, or does not have time for this approach. Its expensive,
but leads to quality releases.
I do not let designers get away with calling a feature complete, till they
have supplied me with an extensive series of pass/fail test for that
feature. These are used to validate the feature, and are incorporated into
the regression test suite. Each bug found and corrected as a result of a
customer reported problem also triggers the generation of a test case, also
for inclusion in the regression suite.
You got to learn from your mistakes, or there's no point in doing it in
the first place.
