c



 

 

The Vuser types are divided into the following categories:

’ All Protocols: a list of all supported protocols in alphabetical order.
’ Application Deployment Solution: For the Citrix protocol.
’ Client/Server: For DB2 CLI, DNS, MS SQL, ODBC, Oracle (2-tier), Sybase
Ctlib, Sybase Dblib, and Windows Sockets protocols.
’ Custom: For C templates, Visual Basic templates, Java templates,
Javascript and VBscript type scripts.
’ Distributed Components: For COM/DCOM, Corba-Java, and Rmi -Java
protocols.
’ E-business: For FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, and
the dual Web/Winsocket protocols.
’ Enterprise Java Beans: For EJB Testing and Rmi-Java protocols.
’ ERP/CRM: For Baan, Oracle NCA, Peoplesoft-Tuxedo, Peoplesoft 8,
SAPGUI, SAP-Web, and Siebel (Siebel-DB2CLI, Siebel-MSSQL, Siebel-Web,
and Siebel-Oracle) protocols.
’ Legacy: For Terminal Emulation (RTE).
’ Mailing Services: Internet Messaging (IMAP), MS Exchange (MAPI),
POP3, and SMTP.
’ Middleware: Jacada and Tuxedo (6, 7) protocols.
’ Streaming: For MediaPlayer and RealPlayer protocols.
’ Wireless: For i-Mode, VoiceXML, and WAP protocols.

c
 





We have to set run time settings before run the script, in run time settings we have to
set log ( there are two options, 1 is send messages when error occurs and second one is
always send messages). In second option we have to select whether it is standard log or
extended log. In standard log it will create log file with some details(information) but in
extended log we can select parameter subsitituion, data retured by server and advanced
trace, based on our selection only the log files will be created. If you want detailed
information related to test run then only you have to choose extended log with
parameter substitution and other options. It will helpful to know full details of that test
run with that extended log file.

c
 

VuGen is a loadrunner component used to generate vuser script i.e here we record a
business operation performed by a single user.

c
 



 

In LoadRunner Analysis, you have to set Elapsed time for getting transaction response
time related to elapsed time. For this you have to use Filter Icon in the Analysis result
file. For ex: the test run is 1 hr but you want the transaction response time from 25 min
to 55 min in that one hr. In Elapsed time you have to set FROM and TO period so that
 you can get the transaction response time in that period only........

c
 




Correlation is the identifying and resolving data which are , unique for each run of the
script or each iteration of an action.

These dynamic data differ in each replay from the original recording and causes the
replay to fail.

c
   

Action that a vuser performs during a scenario are described in a Vuserscript.It also has
function which record the performance of the sever during the scenario


   



!

DB Virtual Users
SAP Virtual users
WEB
GUI
RTE(Remote Terminal Emulators)

c


! 


 " #

Remote Command Launcher is used to Start the application from the Host. Host is a
Computer or Machine


  
 


 

There are 5 graphs on Load Runner.

1) Hits per second graph

2) pages download per second graph

3) Transaction response time (under load) graph

4) Transaction response time (percentile) graph and

5) Network delay time graph

 
!  

  


Initially run the application with one user. Save the results.

now increase the load to 5,15,50,100,500,1000 slowly.

 During the process, you will find the system will break down for a particular number of
virtual users. From there start decreasing the load and u will find the bottle neck for the
application so that u can call for the quality meeting.

c


   


!


 


Wdiff -

This is a Loadrunner tool which can be user to spot the dynamic data to be correlated.

web_reg_save_param (const char *ParamName, <List of Attributes>, LAST);

This is a built in loadrunner function that can be used to find and save occurrences of a
text string (text to be correlated within the Web page) to a parameter.



 


Establish items to be correlated (dynamic value)

Find the left and right boundary of the occurrences of the dynamic value
Add a web_reg_save funtion to parameterise all occurrences of the dynamic value- text
between the left and right boundary.(Remember the escape character where necessary
in the boundary names)
Replace all occurrences of dynamic value with parameter name in curly braces
.Replay to verify correlation was successful

1. Scan for correlation - this gives you a list of data that need to be

OR

1 Compare two scripts recorded identically, using windiff determine the

differences(Dynamic Value) that will require correlation

2. Assuming our application under test has a book flightsbusiness process, and two
recordings of the book flight process have entries for their Flight Numbers as below and
we have determine the value to be correlated is Flight Number: Flight_210 and
Flight_212(in the vugen script).

"Recording A - Name = Flight_210" ,"Value=on", ENDITEM,

"Recording B - Name = Flight_212" ,"Value=on", ENDITEM

Use the "Control +F" Search for all the occurrences of "Flight_210" in the Server
Response Snapshot of Recording A( go to - TreeView -->Server Response Snapshot).
 Search for the number of occurrences of your left boundary until you find your dynamic
value. This number of occurrences is passed to the web_reg_save function as the ORD.

3. Add the web_reg_save_Function("Parameter Name", "LB= <left boundary>",

"RB=<Right boundary>", "ORD=<no of occurrences from above>").

4. Replace all occurrences of dynamic value with parameter name in curly braces.

5. Replay to verify correlation was successful.

c
 

$

Load Runner Agent is the mediator between Load Runner Controller and the Host.

c


!
  

Capturing the end-user activities into automated scripts.

c
 
 




1. VU Generator - For generating VU Script for the type of Vuser under test like DB
Vuser/Web Vuser

2. Controller - For creating scenarios

3.Analysis - For viewing execution results

Based on exp with loadrunner 5.0

c     
 
 

!
!

% 
 !



   
 

When u wanted to run the script 'n' no of times, you need to parameterize the changing
values, according to the requirement. But sometimes, there will be some unique values
which will be generated by the system itself. Those values has to be correleted.

A better live example.

Suppose I have to register 5 students.

1. A script has to be recorded for one student, like entering his name address and the
examination he is taking. Completed feeding details now, and you have to submit the
details. After submitting, you will get a registeration ID , which is unique.

2. You have completed the script now. Now you have to parameterize the student name,
 his corresponding details, so that every student will have their own details.

3. But, you cannot parameterize the unique Id generated by the

system.ie.,registeration Id. So we scan for unique or dynamic values using scan for
correlation. It displays the Reg Id. select it and say correlate.

correlation is done to instruct Loadrunner, not to stop the execution of the script, when it
finds a unique value.

Hope u all might've got my explanation.

Well while execution si going on, making any sort of chnage is not possible. So you cannt
correalte it while execution is going on.

But yes after it stops its possible.

regarding manual correlation, in the script u came across soem uique generated id.let it
be "P-101". So try to find the first occurance of that "P-101" in teh script. once u got
that now this is sure that u have to put the manula correaltion somewhere before this
occurance.

Now the next question is how to find the correct position of the where
web_reg_save_param function need to be used and what teh boundary values.

So for that start moving above in script where u got the first occurance of "P-101". let
consider in script where "P-101" occur the name of html page t11 exist. so the feasiblity
of finding "P-101" in above files is there.
So navigate to Data folder try to find "P-101" in files t1, t2..t10.
generally u find it html/data info pages.

lets consider you find "P-101" in t7 as t8 to t10 were jpg files. so now u ahve to use
web_reg_save_param function just before the function which conatain the name of file
t7.u will get the LB and RB from teh t7 file. take data left and right of "P-101" from t7
files.

Also replace each occurance of "P-101" from script.

hope things might be clear

c
    & '()(((  

The capability of the system to handle 10,000 vusers can depend upon the Memory
footprints of the VUSER. For example the Web http/html protocol can take less resources
compared to a Oracle-NCA Vuser or a winsock Vuser. so determine the Memory footprint
and then you can go about the testing for 10,000 vusers.

Also the transactions can be run as threads or processess>>Believe me this makes a lot
of difference.
c

 
  
 


Transactions are the only means of measuring performance.

c
  

Load runner save the information in a scenario files.

c


   


Manual & Automatic Co-relation

Manual correlation? - Correlation is used to obtain data which are unique for each run of
the script and which are generated by nested queries.
Automatic correlation is where we set some rules for correlation. It can be application
server specific. Here values are replaced by data, which are created by these rules

i obtain the dynamic value in the script but which place is suitable for apply the
web_reg_save_param function in the script

c
 *



Injector is nothing but load generator in LR. when you want to run a script for multiple
Vusers then you have to a create a scenario for those scripts or script with multiple
users. There you have to specifiy the load generator i.e., it is local host or remote host.
it means that from which system you have to ramp up the Vusers to run the script. for
this you have to add the load generators by giving their IP addresses and before for this
you have to install load generators on those machines which are to be used as injectors.

c
  + 

It is a general function which is accessed by all types of users.

this is also called LR function because all general functions start with lr.




, 

 


 
% 

 

 ,

Here is the common process?in ?Load Runner :

1. Plan the Load Test

2. Create Web Virual Users

3. Create Scenarios
 4.?Run Scenarios

5. Analyze the System Under Load.

1. Identify the objectives/goals from performance testing.

a. Define objectives and goals
2. Business requirements and business critical transactions identification
a. Business requirement.
b. Business critical transactions
3. Hard ware/software requirements and location
a. Hardware specifications
b. Software specifications
c. Location of application and perf testing
4. Performance testing tool.
a. Identification of optimistic tool
b. Scripts design process
c. Scripts authoring
d. Results analysis from the tool
5. Procedure/kinds of perf testing need to be performed.
a. Types of Perf runs
b. Objective from each run
6. Identifying bottle necks during perf testing.
a. Application server level
b. Application server box
c. DB server
d. DB server box
e. Load generator
7. Perf results analysis.
a. Analysis of results from the perf tool
b. Analysis from the logs.
8. Areas need to tune after performance run.
a. Fix the bottle neck problems.
b. Re run the perf test.



- 




  



LOAD TESTING: First generate the script using virtual user generator or astra quick test.
Run the generated script in the load runner controller. While doing this run time settings
are to be modified according to the specifications required. Eg. ignore think time, ignore
content in theapplication etc..

In run time settings, choose the numbers of virtual users to run

the application simultaneously. let all the virtual users begin from the same point. Once
you click start scenario the load test begins.

Points to consider after stopping the application:

 1, The number of throughputs and hits per sec have to increase as the number of virtual
users increases. If throughputs flattens, we can say there are network problems and if
hits per second flattens, we say connection/network problems.

2, check that all the virtual users passed the applicationwithin the specified Response
Time.

c

 . 



1. application server monitors,

2. web server monitors,

3. database server monitors and

4. network monitors. They help in finding out the troubled area in our scenario which
causes increased response time. The measurements made are usually performance
response time, throughput, hits/sec, network delay graphs, etc.


  ! 
  

 

When Creating Scenario in Controller we have to add the particular script which we want
to run. There we have to set the number of Vusers to run for that script. but you have to
add Vusers depending on the ur LoadRunner license for how many Vusers it supports

c
 




Parameterization is passing the set of data to anapplication. we have to parameterize the

fields when we want to run the script with multiple users. for example if you scripted the
navigations like entering the data of your data of birth, your place of birth etc. then
suppose if u want to run the script one again (if the data is unique) or when you want to
run the script with multiple users in controller. You have to parameterize those fileds for
safe run.

c    

   /

 

 
 
 /

  

 0(

Loadrunner 8.0 supports .NET based applications.


 

  !   



Yes we can execute winrunner script in load runner. In VuGen u hv option in files to Add
File to Script. Browse the script of winrunner and add to VuGen.

Then you can create a scenario in what ever way you want it.

   




Basically what can be done in this situation is that we can:

Prioritize them according to most used scenarios

Select those that would cause heavy database usage.
Select those scenarios that mostly emulate the user when the application usually go
online.

c
 



Load Runner is an Load automation Tool used to determine the Load of an application,
An Product of Mercury. Usage of this Tool we can find the Load of an Application and the
Bottlenecks of the same of different Layers.<br><br>Though it is costly we can get
more precise information of the above. It is comprised ofGenerator, Controller &
Analysis. <br>

c

 



  



The load runner advantages are<br><br>1.loadrunner reduces the personnel

requirement by replacing the humun users with the vusers(virtual
users).<br><br>2.numarous vusers run on a single computer loadrunner reduces the
hardware requirements.<br><br>3.it allows you to effectively control all vusers from
single point of control<br>

c
  


A scenario defines the events occurring during each testing session. It also defines and
controls the number of users to emulate, the actions they perform and the machines on
which they run<br>

c
     


The vuser is virtual users nothing but those who simulate the real users.The virtual users
who take the place of real users operating client software, such as IE sending requests
using the HTTP protocol to IIS or Apache web servers.

c 

  


As we all know that functionality testing helps ensuring that the product/application
works fine according to the requirements and the client verifications are validated. This
is always done by single user and depending upon the complexity of the application or
the product, many test cases are written to ensure that the components functions as
intended, but when the application passes this TollGate of functional testing, there is
always question of what will happen to the application/product when multiple users are
accessing them. Here comes the load testing which ensures that the application performs
without breakdown for the required users as indicated in the CS ( customer specificatio )
document. For this we need to ensure proper loadtesting is done using automation as we
 all know we cannot ask 50 real users sitting b4 a computer and click is done, moreover
all the areas of concerned will not be covered. One such loadtesting automated tool is
loadrunner which is used to emulate the behaviour of real time user. Here the
loadrunner is used, there are other load testing tools in the market but Mercury stand in
forefront.


 



1.Create a scenario by replacing the VUser script with the GUI WinRunner script.

2.Select Host->Details options from menu

3.Enable the check box for GUI Winrunner(Mandatory to run the WR Script)

4.Execute the Scenario

Note: As you can work with only one instance of the winrunner at a time, the
maximumno of users execute in this scenario is 1.



- 




  



LOAD TESTING: First generate the script using virtual usergenerator or astra quick test.
Run the generated script in the load runner controller. While doing this run time settings
are to be modified according to the specifications required. Eg. ignore think time, ignore
content in the application etc..

In run time settings, choose the numbers of virtual users to run the application
simultaneously. let all the virtual users begin from the same point. Once you click start
scenario the load test begins.

Points to consider after stopping the application:

1, The number of throughputs and hits per sec have to increase as the number of virtual
users increases. If throughputs flattens, we can say there are networkproblems and if
hits per second flattens, we say connection/network problems.

2, check that all the virtual users passed the application within the specified Response
Time.

c

 . 



1. application server monitors,

2. web server monitors,

3. database server monitors and

4. network monitors. They help in finding out the troubled area in our scenario which
causes increased response time. The measurements made are usually performance
response time, throughput, hits/sec, network delay graphs, etc.

   




Basically what can be done in this situation is that we can:

Prioritize them according to most used scenarios

Select those that would cause heavy database usage.
Select those scenarios that mostly emulate the user when the application usually go
online.

 1%   
'  

More than one Vuser can be tested using the Load runner Controller.We can simulate
vusers using this tool and run a scenario using the controller and test scripts based on
many vusers



 
 




 

! 
 

 
  
 
 

Any number of graph like no of vusers,transaction responsetime.But there is no specific

graphs was like ur asking.

c  
2 
 



we used the following funciton for correlation

web_reg_save_param

for ex: web_reg_save_param("outFlightVal", "LB=outboundFlight value=", "RB= checked

>", LAST);

33


, 

 


 
% 

 

 ,

Here is the common process in ?Load Runner :

1. Plan the Load Test

2. Create Web Virtual Users

3. Create Scenarios

4.?Run Scenarios

5. Analyze the System Under Load.

$
.
4

  5(6  
!  

 Performance problem are based on server capacity, database problems, deployment
problems etc...

Depend on the Testing what you are performing ?

IN Performance Testing :

The breakdown of responses from server to client more than the expected message
quote

IN Load Testing/Stress Testing:

The outof Memory Problems

Object Locks at code level
Tables lock at database level
Compatability of the Production version with the auxiliary systems
and etc.......

c
  


 

We can filter the information display only those items that meet the selected
criteria(filter box) .exam you can filter vuser only those who are in ready state. Sorting -
we can sort all the vuser in the vuser list. In order to their vuser ID(1,2,3,4,5,6,7,8,9).

c
  
7


hrough scenario wizard we can create a new scenario.

c

 0 

 !  

 

1-host windows(list of machine).

2-script windows(list of all the vuser script)
3-rendezvous windows.
4-transaction windows(display all the transaction) .
5-output window( display error and notification message).

c

  



c   
7 
 Rendezvous point insert in to the script to calculate the peak load of the server. Syntax.
lr-rendezvous("rendezvousname").

c
  






  


It will end the transaction. Syntax. Lr-end-transaction("transaction name", LR-AUTO).

c
  

 
+



  


t will start the transaction on the script. Syntax. Lr-start-transaction("transaction

name").


  

While editing the script we have to inserting the transaction point and rendezvous point
.

c

  
!  

  

Vugen contain the 3 section .

1-vuser-init
2-action.
3-vuser-end.



  

By recording the activity between client and server.

c
  +
 

Record a log off in to the server (vuser stoped).

c
  

+



Running the script without using controller


 !
 

The important steps needs to carried to enhance a basic script

1. Parameterization( Providing the user inputs to the application)

2. Correlation(handling dynamic server responses)

3. Transaction names( to get the response time)

4. Think time( to simulate the real time user wait time)

 5. Text check( validating the server response pages for the request).


 


!
  


vuser script contains 3 sections

vuser_init: contains the login statements of the script

vuse_actions: contains acton statements performed by vuser

vuser_end:contains log off statements


 


!
  

DB Vuser performs operations against a database server.

Recording a DB V user is as simple as perfoming a business process while having

launched the LR Vugen.

This creates a script which is used by LR to perform the recorded business process.

once recorded , a script is then parameterised.This process involves replacing hard coded
data values in the script with parameters which refers to tables external to the script.

Values can then be placed in these tables allowing Vusers to perform a single business
process , but with different data each time.

c
 .8+


Microsoft's operating system software 'Windows'.

It is different from WinRunner which is Mercury testing tool for GUI.

c
 1% 


  
 

GUI Vusers actually perform the actions using the client.this means that fewer GUI
vusers can be run per workstation than the other types of vusers due to the overload of
the client, and is infact limited to one GUI v user per workstation.GUI Vusers are not so
much to generate load on a system but to test end -to end performance associated with
various business processes.






$

This is auto generated while installing Load Runner.

c

 

  
 There are 5 steps.
1-planning the test.
2-creating the vuser script.
3-creating the scenario.
4- running the scenario.
5-analysis the test result.

c
 



Load Runner Controller easily a siand effectively manages all the scenarios from a single
point of control.