Professional Documents
Culture Documents
Load Runner
Load Runner
Performance for the Load runner: there are 2 categories of testing where usually the block
box test engineers will involve.
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.
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.
Features provided by the load runner it over comes the drawbacks of manual load testing:
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.
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)
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.
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.
1. Load test planning: in this phase the load test lead will do the following.
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:
Enhancements:
Transaction points: transaction points are provided for measuring request or group of request.
Navigation:
Rendezvous point: rendezvous point is used for making all the V-users to perform an action
simultaneously.
Navigation:
Break point: break point is a feature provided by Load Runner which is used for breaking the
execution team par ally.
Navigation:
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
Navigation:
1st style:
Page 6
Navigation: 2
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.
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);
Design the scenario: are can design the scenario using the design tab in the controller
Navigation:
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