Use of a prototype
We are using QTP in our company for testing our application.
We are basically doing record/play of our tests.
For this, we are taking a prototype of the application for recording and configuring the test scripts and then using that script on the actual application. This is certainly a better approach than recording on the first release of the actual application which may contain bugs.
Can someone discuss the benefits and drawbacks of this approach?
Re: Use of a prototype
How fix is the prototype?
In one of my project we had used "Rational Robot", but only to automate the smoke and regressions test. I tried once to automate the test of the new application. But it wasn't effektive. Most of my time i had to fix the scripts, and not to test the application.
But then we used "SQS-Test" (german company www.sqs.de) to describe test cases and dates and translate this automatically in scripts for the robot. The benefits was: if the GUI or the program logic changed, we had only to fix a description in "Test-kadet"(name testcases tool. Then this tool compute the new test cases, activaded "Testdat" to compute the testdata. At the end all was translated in scripts for the robot. With one change we could fix all scripts for our testcases. I loved it!
My two cents worth, when you test a new application with a capture replay tool, you maybe will have numerousness suicides in the company (especially of testers) [img]images/icons/wink.gif[/img]