Scribd
Upload
98 views

Load Runner

LoadRunner is a performance and load testing product that can emulate hundreds or thousands of concurrent users to test a system's behavior under real-world loads. It involves three tools: Virtual User Generator to record and script tests; Controller to run scripts across load generators that simulate users; and Analysis to view test results and generate reports. For example, LoadRunner could simulate hundreds of ATM users accessing a bank server during a peak usage period to identify potential problems before they affect real customers.

Uploaded by

Padmashree Deepak
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
98 views

Load Runner

LoadRunner is a performance and load testing product that can emulate hundreds or thousands of concurrent users to test a system's behavior under real-world loads. It involves three tools: Virtual User Generator to record and script tests; Controller to run scripts across load generators that simulate users; and Analysis to view test results and generate reports. For example, LoadRunner could simulate hundreds of ATM users accessing a bank server during a peak usage period to identify potential problems before they affect real customers.

Uploaded by

Padmashree Deepak
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

LoadRunner is an industry-leading performance and load testing product by Hewlett-

Packard (since it acquired Mercury Interactive in November 2006) for examining system
behavior and performance, while generating actual load. LoadRunner can emulate
hundreds or thousands of concurrent users to put the application through the rigors of
real-life user loads, while collecting information from key infrastructure components
(Web servers, database servers etc). The results can then be analysed in detail, to explore
the reasons for particular behaviour.

Consider the client-side application for an automated teller machine (ATM). Although
each client is connected to a server, in total there may be hundreds of ATMs open to the
public. There may be some peak times — such as 10 a.m. Monday, the start of the work
week — during which the load is much higher than normal. In order to test such
situations, it is not practical to have a testbed of hundreds of ATMs. So, given an ATM
simulator and a computer system with LoadRunner, one can simulate a large number of
users accessing the server simultaneously. Once activities have been defined, they are
repeatable. After debugging a problem in the application, managers can check whether
the problem persists by reproducing the same situation, with the same type of user
interaction.

Working in LoadRunner involves using three different tools which are part of
LoadRunner. They are Virtual User Generator (VuGen), Controller and Analysis.

Contents
• 1 Virtual User Generator
• 2 Controller
• 3 Analysis

• 4 External Links

Virtual User Generator


The Virtual User Generator (VuGen) allows a user to record and/or script the test to be
performed against the application under test, and enables the performance tester to play
back and make modifications to the script as needed. Such modifications may include
Parameterization (selecting data for keyword-driven testing), Correlation and Error
handling.

During recording, VuGen records a tester's actions by routing data through a proxy. The
type of proxy depends upon the protocol being used, and affects the form of the resulting
script. For some protocols, various recording modes can be selected to further refine the
form of the resulting script. For instance, there are two types of recording modes used in
LoadRunner Web/HTTP testing: URL based, and HTML based.

Controller

1
Once a script is prepared in VuGen, it is run via the Controller. LoadRunner provides for
the usage of various machines to act as Load Generators. For example, to run a test of
1000 users, we can use three or more machines with a LoadRunner agent installed on
them. These machines are known as Load Generators because the actual load will be
generated from them (Load Generators were previously known as "Injectors" - the latter
term is still widely used).

Each run is configured with a scenario, which describes which scripts will run, when they
will run, how many virtual users will run, and which Load Generators will be used for
each script. The tester connects each script in the scenario to the name of a machine
which is going to act as a Load Generator, and sets the number of virtual users to be run
from that Load Generator.

LoadRunner uses monitors during a load test to monitor the performance of individual
components under load. Some monitors include Oracle monitors, WebSphere monitors,
etc... Once a scenario is set and the run is completed, the result of the scenario can be
viewed via the Analysis tool.

Analysis
This tool takes the completed scenario result and prepares the necessary graphs for the
tester to view. Also, graphs can be merged to get a good picture of the performance. The
tester can then make needed adjustments to the graph and prepare a LoadRunner report.
The report, including all the necessary graphs, can be saved in several formats, including
HTML and Microsoft Word format.

External Links
• LoadRunner Homepage
• LoadRunner Group
• LoadRunner Architecture and Approach
• LoadRunner Visual Trainings and Tutorials
• LoadRunner Sample Scripts

Retrieved from "http://en.wikipedia.org/wiki/LoadRunner"

You might also like