Wow! Thanks Mark! Excellent info.
Regards,
Wayne
Mark, this is good information. I’m curious about one of the steps – Regression test, test, test – what tools and strategies are people using to automate regression testing?
Testing was carried out using an estimate of path coverage as a percentage. We chose our test data to cover as many of the steps as possible in our flows. At the same time covering all the user requirements.
It is very difficult to get 100% coverage but we achieved approx 75% of all the steps.
In Summary
o brute force strategy.
o white box testing
o can be very effective at ironing out as many bugs as possible before going live.
o It also gives an indication of path coverage of tests.
In the past I have used PureCoverage from ibm good article here. [url=“http://www-140.ibm.com/developerworks/rational/library/298.html”]http://www-140.ibm.com/developerworks/rational/library/298.html[/url]
I don’t think wm gives coverage figures.
Some good things about having a very simple metric are…
o easily understandable
o easy to measure given the right tools
o can be set to an appropriate quality level given cost and time constraints.
80% is very high,
100% bordering on the impossible,