CS378 - LR Module 1

Fundamentals of Load Runner

Idetifying benefits of Load Testing:

1. Prevents costly failures of mission-critical applications
2. Assures performance and functionality under real-world conditions
3. Locates potential problems before your customers do
4. Reduces development time
5. Reduces infrastructure costs

Types of Performance Tests:

1. Component testing - find the behavior and perfornamce of each tier.
2. Load testing - determine whether the system handles anticipated real-world load.
3. Stress testing - find system's breaking point; measure whether system's
environment is properly configured for unexpected, high-transaction volume.
4. volume testing - check stability of system under extended periods of load.

Load Runner Components:

1. Controller - administrative center for creating, maintaining, and executing
scenarios.
2. Load Generators - run the Vusers that generate load on the application under
test (AUT).
3. Analysis - usses the load test results to create graphs and reports that
correlate system information, identify bottlenecks, and performance issues.

Virtual User Generator (VuGen) - records Vuser scripts that emulate the steps of
real users using the application.

Virtual users (Vusers) - emulate the steps of real users. The Vuser script records
the steps that Vusers perform.

Scenario - is a file that defines the scrip to execute, the number of Vusers to
run, the goals of the test, the computer that will host the Vusers, and the
conditions under which the load test runs.

Controller - the machine you designate to manage and maintain your scenarios.

Load Testing Process:

1. Plan Load Test - define goals, analyze system, gather system usage data
2. Create VuGen scripts - record scripts, turn scripts into Vusers by adding test
data and user behavior
3. Scenario creation - create scenarios based on goals
4. Scenario execution - execute scenarios up to 100% load. Follow with over-load
testing.
5. Results Analysis - analyze data and pinpoint bottlenecks.
6. Tweak system based on analysis - fine tune system based on analysis data. Rerun
scenario to test new configuration.