Making the change from WinRunner to QTP8.0
Hey guys. I am the Team manager for my groups automated testing effort. We are making the change to QTP8.0 after 4 years of WinRunner development. I have a few questions and would also like to hear any advice or experiences from others who have made this change. A couple of general questions I have are:
1. How much enhancement code is really needed for QTP? From what I have seen so far it seems that a lot less actual programming code will need to be added compared to WinRunner.
2. Do any of you use the combination of WR and QTP for your testing and have you seen any conflicts with both being present on the test machine?
3. In general what would you say the learning curve is switching from WR to QTP, less or greater.
Lastly any and all experiences with using QTP vise WR are definately appreciated.
Re: Making the change from WinRunner to QTP8.0
Wade -- Lets take the easy one first --
#2: There is no conflict with having them both on the same box. Trying to use them both simultaneously, which is what will happen if you blend assets, is fine by design, but you will want to make sure you have hardware that is up to the task.
#1: I have personally used both of these product for over 5 years...back before Astra even. I prefer QTP in most situations. However, the answer to your question depends on three primary considerations: First, your application. If it is Standard X, and X is a supported environment in QTP, then you will find the out of the box support excellant. If not, for instance if you try to test a Delphi app with QTP, you will likely be feeling like it is WinRunner, with a different syntax. Second, your test methodology. As a consultant, I see clients try to do all kinds of things; QTP is very flexible, and you CAN do whatever you like...but it's name is QUICK test pro, and that is the design philosophy. When you begin to trade of ease of use for other considerations, you begin to put more of the burden back on your own shoulders. When you begin to directly violate design principles, you put all the burden on your own shoulders. Third is your test goals. If you want end user business process based testing, then QTP is ideal. If you want under the skin, grey box, API testing, that will be a lot more work.
#3: WR to QTP should be a snap. The basic paradigms are very similar...once you know programming, syntax is just a different way of expressing the same thought...and unless you are a real gearhead, you will like a lot of the streamlined functionality. You may not like the Object Repository as much as the GUI map, but there are ways to deal with that as well.