Author:Chaitanya M Bhatt

If your integrating QTP with LoadRunner, the only advantage compared
to RDP protocol is that the rate of success of replays of your
workflow script would be higher due to object recognition capability
of QTP(strictly avoid using analogue mode of recording, which would
defeat the whole purpose of this ordeal!)

Remember QTP approach never gives accurate transaction response time
results what so ever! All the client side activities like page
rendering time, client side internal processing time etc. would be
added to your response time.

Using QTP with LoadRunner is challenging. But I would like to give you few tips to make your job a little more simpler.

1. Make sure of the reason why you have chosen QTP approach. (This is very
very important.)
2. Now that you’re sure you’re left with only one option, make sure
you know the limitation of this approach.(also make sure the client is
informed about this!)
3. Make sure you have Windows NT installed on all the LoadGenerators
(Server OS can allow multiple user accounts to be created, which can
help you reduce total number of LoadGenerators. Example: 1
LoadGenerator with 32 Gb of memory and 2 quadcore processors with
Windows NT or Windows 2003 can probably have approximately 15 user
accounts with QTP installed seperately on all the user accounts.)
4. In the controller loadgenerator options, make sure you have atleast
2 or more terminals per session enabled in your terminal session
manager. This can help you spawn more than one qtp session on one user account.
( This option is very tricky! Do a very detailed proof of
concept before you go ahead with this.)
5. Make sure you have good amount of think time between page loads
which can help you avoid page sync failures.