Course information:

Course: HP Load Runner Test Automation Training
Trainer: Certified
Date: 2018 Jan 12-14
Duration: 3 days (9:00-17:00)
Location: Chandigarh Centre
131-132,  Sector 34 A, Chandigarh, India

​

HP Load Runner is an all-in-one solution for testing and optimizing enterprise applications. With a diversity of users in mind, LoadRunner enables developers, QA engineers, business analysts, architects, and performance testing teams to ensure that software applications will scale to support the right number of users, transaction volumes and performance levels. As a leading automated test solution, LoadRunner vastly improves mean-time-to-resolution.

 

Intended Audience for this HP Load Runner Course in Chandigarh

​

• Quality Assurance Engineers

• Performance Engineers

• New users of LoadRunner who need to test the performance of their applications and/or executives who will be involved in any part of performance testing

​

​

Prerequisites for HP Load Runner Course in Chandigarh

​

• Knowledge of the Windows 2000 or Windows NT interface and environment

• High-level knowledge of the Web and or client/server environment

 

ISTQB Foundation Extension Agile Tester Course Objectives

​

• Get an accurate picture of end-to-end system performance prior to going live.

• Support your organization in verifying new or upgraded applications against performance specifications.

• Ensure scalability by identifying and eliminating bottlenecks.

• Get faster, more reliable application deployment with lower business risk in production.

• Optimize assets utilization.

 

LoadRunner Course Outline

 

The Fundamentals of LoadRunner

​

Day 1

1) Planning an Effective Load Test

a. Define measurable goals for testing
b. Gather information before testing
c. Document and organize system information

2) LoadRunner Installation

a. LoadRunner architecture
b. Where to install LoadRunner components
c. Identify hardware and software needed for installation

3) Introduction to Scenarios

a. Explain elements that make a LoadRunner scenario
b. Identify different types of scenarios
c. How to choose the scenario
d. Present the basic steps for creating a scenario

4) Using Run-Time Settings

a. Script and Scenario Run-time settings
b. Configure Run-time settings in the Controller

Day 2

5) Scenario Execution

a. Prepare for a scenario run
b. Identify techniques to efficiently run a scenario

6) Scheduling Scenarios

a. Scheduling by group and by scenario
b. Prepare VuGen User (Vuser) initialization
c. Configure duration scheduling
d. Configure scenario ramp up and ramp down

7) Performance Monitors

a. Value of Performance Monitors
b. Select Performance Monitors
c. Add measurements to Performance Monitors

8) Results Analysis

a. Value of root cause analysis
b. Diagnose errors with LoadRunner
c. Meaningful interpretation of LoadRunner graphs

The VuGen Scripting for web

Day 1

1) Recording

a. Structure the script based on planning
b. Use VuGen to record a Vuser script for Web
c. Describe HTML and URL recording levels
d. When to use HTML and/or URL recording levels

2) Playback

a. Identify the appropriate Web Run-time settings to set
b. Configure Web Run-time settings to run the script
c. Verify Vuser script functionality in VuGen

3) Actions and Transactions

a. Create multiple actions in a Vuser script
b. Configure actions to achieve load testing goals
c. Add Transactions to measure response times

4) Parameters

a. Solve playback problems by parameterizing the script

 

Day 2

5) Checkpoints

a. Identify visual cues to check for during load testing

6) Add Text Checkpoints during and after recording Manual
Correlation

a. Distinguish between available correlation methods
b. Correlate a script manually using correlation functions

7) Correlation During and After Recording

a. Correlation after recording
b. Use the Scan for correlation tool
c. Correlate data during recording
d. Define rules for correlation in Recording Options
e. Enable correlation during recording

Day 3

8) Enhance Vuser Output Log

a. Send customized output messages to the script
b. Execution and Controller log
c. Add error handling and business logic to the script

9) Advanced Error Handling

a. Create global verification points with ContentCheck
b. Use “logging on demand”
c. View error snapshots in the