This article has been submitted by Prarthana Agwania. This is an Article dealing with advance concepts of Load Runner and QTP. This Article assumes that you have working knowledge of both QTP and Load Runner.
Many of you might be aware of the automation testing which requires some automation tool. For Siebel applications, we mostly use HP (formerly Mercury) Quick Test Professional (QTP) for Functional Testing and HP LoadRunner(LR) for Performance Testing.
Though for Performance Testing, LR scripts are prepared from scratch. In our project we provide Click stream documents or Webex recording in order to provide the flow for the functionality.
But the efforts can be saved by converting QTP scripts to LR scripts or rather to be very precise invoking QTP scripts from LR and then capturing the replay of QTP scripts through LR thus resulting in LR scripts.
There can be two approaches to make this possible:
- Using QTP Script directly to run the Load Test using LoadRunner
- Using QTP Script to generate LR Script and then using the same to run a Load Test.
Follow the steps given below to Run QTP Scripts directly using Load Runner
- Prepare a QTP script.
- Install QTP on a Load Generator machine.
- Setup the Load Generator machine for Terminal sessions.
- Create a controller scenario using QTP script.
- In the Load Generator details, choose the Virtual User ( vuser) limits tab and increase the GUI limit.
Now you are all set to start the test. But the method has its own constraints.
Since Load Test requires to have a large amount of load in the form of no. of virtual users performing a certain task, QTP has its limitation of taking the full control on GUI desktop of a computer. So that means only one QTP script can be run per computer which implies that we will require that many physical computers in order to run multiple QTP scripts.
The problem can be overcome by using Terminal Server or Citrix Server or VMWare which will generate number of virtual desktops on a single machine. But here comes another issue of licenses. LoadRunner requires a GUI vuser license to run QTP scripts in the controller. Running each vuser requires a separate GUI vuser license.
Readers please note: Some of you might be thinking that we need to have QTP licenses as well in order to open that many instances of QTP. This is not the case. You only have to have GUI vuser licenses.
<< Previous in series Next in series >>
(No Ratings Yet)
Loading ...
2 Comments at "QTP and Load Runner Scripts - Part 1"
Interesting explanation!
Also, I wrote the similar article on running QTP from LoadRunner:
Run QTP from LoadRunner
But your explanation is more dipper and contains important details. Thanks!
I am currently using Merchury LoadRunner 7.6 V to test Oracle 11i application. I selected Oracle NCA and Web protocols and recorded a basic script to query an order. I recorded in HTML mode. When I replayed back, it runs successfully sometimes and other times throws error message saying
Action.c(72): Error -24998 : nca_obj_type(”607″) failed, Window or object is not displayed.
The window currently in focus: “Error”
vuser_end.c(4): Error -24998 : nca_menu_select_item(”Sales Orders”,”File;Close Form”) failed, Window or object is not displayed.
The window currently in focus: “Error”.
I co-related icx_ticket and played back. But still getting the same error.
I would like to know from you in order to resolve this issue, do I need to do some co-relation or it needs some basic settings in Oracle Apps before recording an action in LoadRunner.
Comment Now!