Tracking Transaction Response Time in GUI Vuser

In our earlier post, we’ve mentioned that Quick Test Professional (QTP) scripts can be used in load testing in LoadRunner.  The scripts are developed in QTP and port into LoadRunner for usage where they are called GUI Vuser.  Executing GUI Vuser in a load test requires the GUI Vuser protocol.  One of the key features of LoadRunner scripts is the ability to track the timing of your individual transaction in the script and generally, you will want to perform the same tracking in the GUI Vuser script. Read the rest of this entry »

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. Read the rest of this entry »

Introducing SAPGUI protocol in LoadRunner

Performance testing recording and execution for SAPGUI relies on the SAP Scripting API and ActiveX the SAP R/3 application server and on all SAP GUI clients that are participating in the load test. As of date of this article, LoadRunner documentation does not have updated details on configuring SAPGUI for scripting such as supported versions.  However, the configurations are somewhat similar to other performance testing product which in this article, we refered to IBM instead.

Read the rest of this entry »

Which protocol to use?

Typically for newbies, the question after getting their first copy of LoadRunner and installation of Vugen will be, “Which protocol to use?”. They post online or to the support to ask, “I’ve got a Java/.NET applicaton, and there are many protocols from the list of Vugen. Which Protocol should I choose ” or “…can you advise on the protocol to use?”.

The fact is that it doesn’t really matter the type of language that was used to developed the application, but rather the type of communication method or protocol that the application is talking to the server. Previously, in “What’s LoadRunner?”, we mentioned that the tool captures network traffic while recording which is the core understanding that we must align when using this tool. Read the rest of this entry »

LoadRunner licenses

LoadRunner requires license to function. The license entitles to (1) the protocol the user is permitted to run, (2) the number of Vusers (or concurrent users it can generate) and (3) the type of monitors available to the user. After LR8.1 FP3 (standing version of this writing is LR9.0), the license model have changed from individual or group protocols to Bundle Licenses. In a Bundled License, the protocols of the same genre are grouped together (e.g. Web (HTTP/HTML), FTP, Winsock are grouped together into Web & Multimedia Bundle). This (in my opinion) provides a neater way to manage the licenses. Also, the all monitors are made available as “All Monitors” with exceptions to the diagnostics modules (e.g. J2EE, .NET, SAP, etc.). Read the rest of this entry »