LOAD RUNNER

Performance for the Load runner: there are 2 categories of testing where usually the block
box test engineers will involve.

1. Functionally testing 2. Non functionally testing

1. Functionally testing: in this category one will perform testing on the functionality of the
application
2. Non functionality testing: In this category of testing one will perform testing on the non –
functional areas followed.
I. Comparability testing
II. Installation testing
III. Usability testing
IV. Volume testing
V. Performance testing

Performance testing: it can be divided in to 3 types

I. Load testing
II. Feature performance testing
III. Stress testing

Load testing: it is a type of testing in which one will apply some initial load, gradually
increases the load in order to find the critical load. Once the critical load is found then they will
comparative with the target load. If at all the critical load gather than are equal to target load then
it is concluded by the load test is pass other wise fail.

Critical Load: the load beyond which application start degrade with performance is known as
critical load.

Target Load: the customer expected load is known as target load.

Page 1
Feature performance test: it is a type of testing in which one will apply predefined quantified
request and calculate the responds time. If at all the response time less than or equal expected
time than the feature performance testing is pass otherwise fail.

Stress testing: it is a type of testing in which one will perform some abnormal action or use the
application continues for long period of time in order to check the stability of the application.

Draw backs of manual load testing:

 More number of human resources required

 Simultaneous action are important
 Co operation and co ordination are missing
 Can’t repeat the same task again and again in same task.
 Proper monitoring system is busy.

Introduction of Load Runner:

Type of the tool  performance tool

Company  Introduce by mercury interactive corporation & taken over by HP

V user scripting language  version 8.0

Features provided by the load runner it over comes the drawbacks of manual load testing:

 V users concept over comes the human resources problem

 Rendezvous point over comes the simony tentative problem.
 Load runner controller over comes the co- operation and co- ordinate problem.
 Recording & playback facility over comes the repetitiveness problem
 Load runner agent overcome the monitoring system problem

Load Runner Architecture:

L R- Agent process V-user generator

Load runner agent LR - controller

V - users Analysis

Host

Page 2
V – User generator: it is used for generating the basic script enhancing the script checking
whether the scripts properly or not and saving the script in terms of a task.

L.R controller: it is vital compound of a l.r which is used for the following.

 Controlling the whole load of a load testing process

 Designing the scenario
 Executing the scenario

Scenario: it is defined as a situational package which describes how many no.of V-users

need to be generate to which machine perform what task and for how long duration. (or)

Scenario is defined a simulated real time situation.

L.G 1

25 V-user

Main machine T1

L.G3

L.G 2

10 V -users 15 V-user

T1 T1

Load Runner agent process: it will receive a request from the LR controller and launch the LR
agent.

LR agent: he is also widely it which will do the following

 It will generate no.of requirements

 It will make them re use the perform the required task
 It will monitor each and re user during the execution
 It will send the observed information back to the LR control semantically
 Finally one the work is done it will kill the re-users.

Page 3
Analysis: the analysis component will receive the consul dated raw result from the L.R
controller and converts them in to easy understandable report & graph so that one can easily
analyze the results.

Load Runner Life Cycle:

1. Load test planning

2. Creating the tasks
3. Designing the scenario
4. Executing the scenario
5. Analyzing the result

1. Load test planning: in this phase the load test lead will do the following.

 He will identify the components of load testing lab

 He will estimate how much minimum load can be generated by each machine
 He will analysis the components
 He will analyze the peek timing &half peek timing of the application
 He will analyze the climate conditions
 He will plan the no.of scenarios need to be designed & executed
 He will plan the initial load to be applied
 He will plan the loads to be gradually increased
 He will do the resource planning
 He will do the scheduling
 He will prepare load test plan document with all the above analyzed information.

2. Creating the Task: in this phase one will generate the basic script, enhance the script&
save it in terms of a task using virtual user generator.

Once a new test is opened in virtual user generator we can find 3 blocks in it

1. V- user init
2. Action
3. V-user – end

V-user in it: whenever any task to be performed only once in the starting of execution then the
related script need to be generated in the v-user init block.

Action: whenever same task need to be performed repeatedly again &again for same long
duration then the corresponding script can be generated in the action block.

V-user End: whenever a task need to be performed only once at the end of the execution then
the related script need to be generated in the V-user end block.

Operational over view of running: during the execution Load Runner will not do any actions
on the front end applications. It will send the equal ant request directly to the server.

Page 4
 Navigation for showing the browser during replay:

 Activate the menu item tool

 Select the option general option
 Select the display tab
 Select the check box show browser during replay
 Click on ok

Enhancements:

Transaction points: transaction points are provided for measuring request or group of request.

Navigation:

 Keep the cursor in desired location

 Activate the menu item insert
 Select the option start transaction
 Specify the transaction name
 Click on ok

Rendezvous point: rendezvous point is used for making all the V-users to perform an action
simultaneously.

Navigation:

 Keep the cursor in the desired location

 Activate the option Rendezvous
 Specify the rendezvous point name
 Click on ok

Comments: comments are used for increasing the readability of script

Ex: /* *hai *hello *bye */

Break point: break point is a feature provided by Load Runner which is used for breaking the
execution team par ally.

Navigation:

 Keep the cursor on the desired statement

 Activate the menu item insert
 Select the option toggle break point

Check points: there are two check points inn Load Runner

1. Text check
2. Image check

Page 5
1. Text check: it is used for checking whether the expected text is responding by the server
whenever it is under load.
Navigation:
 Beep the cursor in the desired location
 Activate the menu item insert
 Select the option new step
 Expand the web checks
 Select the option text check
 Click on ok
 Specify the expected text
 If required specify the right of & next of text
 Click on ok
2. Image check point: it is used for checking whether th e expected image is responded by the
server whenever it is under load
Navigation:
 Keep the cursor in the desired location
 Activate the menu item insert
 Select the option new step
 Expand web checks
 Select the option Image check
 Click on ok
 Specify the after native image name
 Specify the image server file name
 Click on ok

Parameterization: it is a process of replacing the constant values in the script with variables

or parameters in order to increase the scope of the test.

Navigation:

1st style:

 Select the desired constant value in the script

 Right click on it
 Select the option replace with a parameter
 Specify the parameter name
 Click on ok
 Select the parameter & right click on it
 Select the option parameter properties
 Specify the desired value with the help of edit with note pad
 Specify the column setting
 Specify how to select the next row
 Specify when to update value
 Click on close

Page 6
 Navigation: 2

 Activate the menu item V-user

 Select the option “parameter list”
 Click on new
 Specify the parameter name
 Click on create a table
 Specify the values with the help of edit with note pad
 Specify the column settings
 Specify the now to select next row
 Specify when to update value
 Close the parameter list window
 Select the constant value in script
 Right click on it
 Go to use existing parameters
 Select the desired parameter name.

Co-Relation: correlation is a process of capturing the dynamic data generated by the server &
using that data. In the script when ever required in order to made the script execution successful
on the highly secured applications also correlation can be done in 3 stages.

1. Automatic correlation during recording

2. Automatic correlation after executing the script at least once
3. Manual correlation

1. Navigation for automatic correlation during recording:

 Activate the menu item tools

 Select the option recording option
 Select correlation option
 Select the check box enable correlation during recording
 Click on ok

2. Navigation for correlation after executing the script at least once:

 Activate the menu item V-user

 Select the option scan action for correlations
 Go to correlation results window
 Click on correlation all button

3. Steps for Manual correlation:

 Record two identical steps

Page 7
  Compare those scripts with “w diff” tool (tool < compare with V-user)

Replace the required constant with variable & write the following steps on top of
that web-req-save- para(“{ variable name}”, LB = ………..”, “RO = .”, LAST);

Think time: think time is just like wait statement in QTP which makes the V-users wait between
request & request In order to simulate the real usage of server by real users.

Syn: lr-think-Time(17);

Navigation for replaying the think time:

 .activate the menu item V-user

 Select the option runtime settings
 Select the option think time
 Select the option replay think time & also sub options
 Click on ok

Design the scenario: are can design the scenario using the design tab in the controller

Navigation:

Click on add group

Specify the group name
Specify the V-user quantity
Specify the load generator name
Specify the task
Click on ok
Click on edit schedule
Select the one of following options
o Schedule by scenario
o Schedule by group
 If at all schedule by scenario is selected do the ramp up, duration, ramp down settings

 If at all schedule by group is selected do the start time, ramp up, duration & ramp down
 Settings individually for every group
 Set the scenarios start time
 Click on ok

Executing the scenario: it can be done using the run tab in controller

Analyzing the results: analyzing the results can be done with the help of analyze is component.

Once the analysis is done the load runner is provides facility to create the reports.

Navigation:

Page 8
 Activate the menu item reports
 Select the option Microsoft word report
 Fill all the required field
 Click on ok.

Once the reports is prepare add the required conclusion to it and send to the
technical department.

Page 9