Using QTP with LoadRunner for Load Testing

In this post, we shall cover the basic knowledge of using Quick Test Professional (QTP) for load testing with LoadRunner.   Unlike conventional protocols in LoadRunner where you record in Vugen, modify, port into Controller and run the execute button, you will need to do a few more stuff in order to get the setup right and running.   This knowledge will aid you in planning, budgeting, finding resources and minimizing any hiccups when setting up for such load test.

• QTP scripts are developed in QTP not in LoadRunner Vugen – You won’t be able to record and replay a QTP script in Vugen.  All the recording and modification has to be done on QTP.  Once the modification of the QTP script is completed, it will be ported into LoadRunner Controller as GUI Vuser for load testing.
• QTP is required to install in the Load Generators (LG) – The load generators will be required to install QTP as they are used to run the scripts.
• Load Generators will be required to set the same resolution to the machine that developed the QTP script – As QTP is object sensitive, the resolution of the LG is required to be the same with the machine that was initially used to develop the QTP script to avoid any problems arising from missing objects (due to a different resolution)
• [1] GUI Vuser license is required for LoadRunner and QTP concurrent license is required for QTP – This is the 1^st setup approach and budgeting for your licenses.  The total amount of Vuser that you wanted to generate will be the same for both LoadRunner and QTP.  Meaning, if you want to run 50 concurrent users using GUI Vuser protocol, you will need 50 GUI Vuser license and 50 QTP Concurrent license.  In this setup, the LG will create 50 instances of QTP to run the GUI Vuser.  This is described in “What licenses are required to run a scenario with GUI Vusers” from HP Software Support.
• [2] GUI Vuser license is required for LoadRunner, QTP seat/concurrent license is required for QTP and Windows Terminal License is required for Windows – This is the 2^nd setup approach and budgeting for your licenses.   For a 50 concurrent user load test, you will need 50 GUI Vuser protocol, 50 Windows Terminal License and 1 QTP license.  In this setup, the QTP license is merely used to develop the script.  The LG will create 50 remote desktop connections and each of these connections will run 1 GUI Vuser.  This setup utilizes remote desktop functionality to emulate the virtual users.  I believed that HP Support does not really state about the licenses required from Windows Terminal and this is additional cost for you to factor if you are going though this mode.  Personally, I experimented using Windows Server 2003 (that is capable of 3 remote connections by default) with this approach and it works for me.  On the server, the remote connections are established and the QTP script launches the browser for testing.  (I wonder if this is permissible in the first place and like to know if anyone else is doing it.  If you got some input on this, please feel free to shout it here!)

With the above information, you should be slightly more familiar with Quick Test Professional (QTP) integrating with LoadRunner.  However, there may be more things that need to be considered and I may have left out.  Do feel free to feedback and experiences and anything that I missed out when using QTP in load testing!

Related Posts

• Tracking Transaction Response Time in GUI Vuser
• Do you know you can work on the parameter files directly?
• Introducing SAPGUI protocol in LoadRunner
• LoadRunner licenses
• Combining non-standard protocols in a single script that are not listed in Multi-Protocol selection
• What’s QTP?
• Planning for a Load Test
• Monitoring SAP in LoadRunner
• How-to configure Oracle Database monitoring
• How-to configure Sybase monitoring