LOAD RUNNER By Trushal Muthiyal

INTRODUCTION
LoadRunner is a robust performance testing tool widely used in the software testing domain.

Developed initially by Mercury and later acquired by HPE and MicroFocus, it has become a market leader with
approximately 85% market share.

LoadRunner supports various protocols, making it versatile for testing

Its architecture involves simulating virtual users (VUsers) to replicate client

Understanding LoadRunner’s capabilities is essential for effective performance testing!

VUsers are virtual entities created using LoadRunner's scripting language, parameterized to simulate different
user profiles, and distributed across load generators to simulate concurrent user activity.

VUsers offer benefits such as resource efficiency, hardware savings, scalability testing, consistent behavior, and
stress testing.

They enable efficient, scalable, and consistent performance evaluation of applications, reducing human
resources and ensuring reliable test results.
 LOAD TESTING PROCESS
1. Script Creation:
• VuGen (Virtual User Generator) is LoadRunner’s dedicated component for recording business
flows.
• In VuGen, you create scripts by recording user interactions with the application.
• These scripts simulate user behavior during load testing.
2. Scenario Creation:
• A scenario defines what and how to execute the test.
• It includes details such as the number of virtual users, their behavior, and the load distribution.
3. Test Execution and Monitoring:
• In this step, you simply “Run” the created scenario.
4. Result Gathering and Analysis:
• Once the test completes, gather the results.
• Identify bottlenecks, performance issues, and areas for improvement.
5. Reporting:
• Create comprehensive reports summarizing the test results.
• Include graphs, charts, and key performance indicators (KPIs).
 RUNTIME BEHAVIOR
SETTINGS

LoadRunner's runtime behavior settings include pacing, think time, browser emulation, and content checks.
Pacing controls the delay between actions performed by virtual users, ensuring the system doesn't overload.
Think time represents the time a real user spends thinking between actions, showcasing realistic user behavior.
LoadRunner emulates a real browser by mimicking user-agent strings and cache behavior.
It also allows for user-agent selection, browser cache behavior, and content checks.
Careful configuration ensures accurate performance testing results.
By adjusting these settings, LoadRunner ensures accurate test scenarios.
 CREATING LOAD TESTING
SCENARIOS
LoadRunner is a tool for creating load testing scenarios, covering both manual and goal-oriented scenarios.
In manual scenarios, users design the scenarios based on performance metrics.
To create a manual scenario, open LoadRunner's Controller, create a new scenario, and configure
inputs such as the number of virtual users (VUsers),
test duration, ramp-up and ramp-down, steady-state period, and expected transactions
per second (TPS) metrics.
LoadRunner executes the test based on these settings.
In goal-oriented scenarios,
users specify targets and let LoadRunner adjust the load dynamically.
They create a new scenario, set targets like transaction response time, virtual load,
and transaction times per second (TPS), and execute the test. If the targets are unreachable, the execution stops.

Group attributes for scripts allow capturing multiple dynamic values using the same regular expression.
When using `web_reg_save_param_regexp`, specify the parameter name and regular expression to capture the
dynamic data.
The Group attribute saves the entire expression along with the specified text, with a maximum value of 10.
ANALYZING LOAD TESTING
RESULTS
1.Performance Insights:
1. Load testing provides valuable data on response times, throughput, resource utilization, and error rates.
2.Bottleneck Identification:
1. Load testing reveals bottlenecks—areas where the system struggles to handle the load.
2. Analyzing these metrics helps uncover performance issues, such as slow transactions or overloaded
servers.
3.Scalability Assessment:
1. Load testing results help assess system scalability.
2. Identify the breaking point (maximum load the system can handle).
4.Controller Run View:
1. The Controller in LoadRunner provides a real-time view during test execution.
2. Adjust test parameters if needed based on live data.
5.Analysis Window:
1. After the test completes, use the Analysis component.
2. Key features include:
1. Transaction Summary: Overview of transaction performance.
2. Graphs: Visualize trends (response time, hits per second, etc.).
3. Percentiles: Understand response time distribution.
4. Correlation: Identify patterns and correlations.
THANK
YOU