LoadRunner

• Why should you automate performance testing?
 Does the application respond quickly enough for the intended users?
➤ Will the application handle the expected user load and beyond?
➤ Will the application handle the number of transactions required by the
business?
➤ Is the application stable under expected and unexpected user loads?
➤ Are you sure that users will have a positive experience on go-live day?
• What are the LoadRunner components?
 VU Generator captures end-user business processes and creates
an automated performance testing script, also known as a virtual user script.
 Controller  organizes, drives, manages, and monitors the load test.
 Load Generators  create the load by running virtual users.
 Analysis  helps you view, dissect, and compare the performance results.
 Launcher  provides a single point of access for all of the LoadRunner
components.
• Understanding LoadRunner Terminology
Scenario: A scenario is a file that defines the events that occur
during each testing session, based on performance requirements.
VUsers: In the scenario, LoadRunner replaces human users with
virtual users or Vusers. Vusers emulate the actions of human users
working with your application. A scenario can contain tens,
hundreds, or even thousands of Vusers.
VUser Script: The actions that a Vuser performs during the scenario
are described in a Vuser script.
Transactions: To measure the performance of the server, you define
transactions. A transaction represents end-user business
processes that you are interested in measuring.
• What is the load testing process?
• Load testing typically consists of five phases: planning, script creation, scenario definition, scenario execution, and results analysis.
•
 Plan Load Test
 Create Vuser Scripts
 Define a Scenario
 Run a Scenario
 Analyze the Results.
• Load Runner supports over 40 types of applications. e.g: Web, etc.