Re: Automated Testing Success Stories?
User Carl Nagle (Carl.Nagle@sas.com) posted:
That sounds great!
Especially being able to break even in a single production cycle.
In the event that the next production cycle is completely different, you theoretically would still be in the black even if you had to start over from scratch. Many groups don't hit that break even point until two or more production cycles.
I suppose my best story is that we have tests that are automated via the DDE that otherwise would not be performed--period. Too time consuming and mentally exhausting despite their value.
Automated Testing Success Stories?
User Randy A. See (RandLSee@aol.com) posted:
Wondering if those out there who are having success with automated testing
(Mark, Tomba, Carl, others) would be willing to share some positive
statistics. We all have our nightmare stories to share, but I think I
finally have a postive one. Currently I am testing a fairly simple C
application using the keyword-driven or test plan driven methodology as
documented by Zambelich in his white paper. I have 47 scripts which test
1600 test cases. My scripts run in an hour and 15 minutes and I estimate
they replace approximately 80 hours of manual testing. I currently have 55
pages of manual test documentation which support the automatic scripts. It
took me 4 weeks to write the scripts, including source code, so once I ran
them twice I hit the break-even point as far as return on investment. You
know, sometimes this stuff really does work, even if it is a Rational