| || |
We are going to evaluate QTP soon. Could you tell me what set up we need before our external QTP expert comes? We want to have a right set up when he comes. Our application is java client application.
Could you also point on anything helpful in regards to QTP vs. Rational Robot - we will be evaluating Robot as well.
If anyone of you have an example of Proof of concept on QTP or any example of documents related to tools evaluation process I would really appreciate. I hope you understand what I am going through. Definitely not an easy job to propose the tool to the management and convince them we are making the right decision.
Thanks in advance
Re: Evaluating QTP
Too bad we could not meet.
I did a POC when I worked for a bank here in New York. We looked at Rational, Mercury, Compuware, and Segue, for both function and load testing. We had a book of what we wanted them to perform and how to do it like, "in this screen you must use the DDLB", "in this screen you can't use coordinates", "here you must use an input file" and so on. To answer your question now "No" I did not get any of the documents when I left. The entire process took about 3 months and each company had one week to do as much as they could. Then we put everything back the to the same starting point and did not tell the next company what the last one found and where their problems were. We also had a check list of what they did and did not do, and a grading system of how well they did it.
I'm now doing the same thing where I'm working now and we are going to look at everyone again but Rational.
My suggestion is after your letter requesting a POC and the confidentiality agreement is signed. You need to manual script what there are to do and send it to them so they know how detailed your going to be. Also to make this fare don't talk about each vendor and there problems.
We can take this off line if you like.