c





  

 
c



 
 






 

‘




‡ 
  
± An advanced protocol for modern JavaScript based applications
(including Ajax) emulating user activity within a web browser. Scripts are developed
interactively in Mozilla Firefox.
‡  
± A new protocol for Silverlight based applications emulating user activity
at the transport level. Allows generating high level scripts by automatically importing and
configuring WSDL files used by the application.
‡ 


‘ ± A new protocol designed to record java-based applications and
applets. It produces a Java language script using web functions. This protocol is
distinguished from other Java protocols in that it can record and replay Java remote
calls over HTTP.
‡  
‡ The Citrix Protocol now supports Citrix Online Plugin versions 11.2 and 12.0.
‡ Added support for Citrix XenApp Server 5.0

 
 
± NCA Java object property support now provides automated creation
and registration within a script of a query-answer table of communication between
client-side Java objects and the Oracle NCA server.
‡ ‘ ± Added support for SAPGUI for Windows Client version 7.20.
‡  
 ± The LoadRunner Controller can run scripts created in HP Service Test
11.00, HP¶s solution for creating and running automated tests for SOA and headless
technologies. Refer to the Service Test documentation for details of creating Service
Test scripts for a load testing scenario.

 

‡ 




! ) ± Enhanced data format capabilities for the Web
(HTTP/HTML) protocol family. Allows converting raw HTTP traffic into a maintainable
and structured XML format and enables correlations by XPATH.
‡


"

# Web (HTTP/HTML) automatic correlation mechanism has been
enhanced to search for possible correlations in the larger scope of snapshot data
created during code generation including data formatted by DFE.
‡ $

%& ± New snapshot view for Web (HTTP/HTML) protocol steps allows
viewing complete HTTP traffic in both raw and DFE generated formats.

% ± HP ALM Integration ± Enhanced integration with HP Application Lifecycle
Management platform that serves also Quality Center and Performance Center editions.

'"
&
$$
 ± Added support for Windows 7 and Windows Server 2008. See
below for limitations.
‡ (
)$
 ± Enhanced Analysis reports are more customizable. Analysis data
can be exported to a variety of formats, including Word, Excel, PDF, and HTML. New
report templates allow saving report definitions and generating reports based on a
template.

ÿ 














 







 
 




 
 
c 
!
 
"
#
 
 




!










How to design a Scenario for Load testing using HP ±

LoadRunner?
Brief Introduction of Scenario: A scenario is a file containing all the information about groups
of Vusers which emulate human users during our testing session.

It is a means through which we emulate a real-life user. When we run a scenario, the Vusers
generate load on the server, and LoadRunner monitors the server and transaction performance.

u
ective of this Tutorial: Is to design a scenario, which can be used to test an application
under load. For illustration purpose, we shall create emulate the actions of say ten travel agents
concurrently using the flight reservation system and analyze the performance of the system under
load.

We shall create a scenario, which will emulate various actions performed by a group of ten travel
agents. The user actions can be simultaneously logging on to the system, searching various
flights, purchasing the desired flight tickets, checking itineraries and finally logging off the
system.

Basic steps for designing a scenario for load testing are as under

Step ± 1: Launching LoadRunner & its Controller Module:

a) Open the HP LoadRunner Launcher window by clicking ³Start´ > ³Programs´ >
³LoadRunner´ > ³LoadRunner´.

) Open the LoadRunner Controller by clicking ³Run Load Tests´ In the ³Load Testing ta ´.
³New Scenario dialog ox´ shall open. Here we shall be able to select scripts for our new
scenario.

Step ± 2: Making a selection of method of creation of scenario: out of two methods like 1)
Manual Scenario 2) Goal-Oriented Scenario ± in case we wish LoadRunner to create a scenario
for us.

In this tutorial we shall select a ³Manual Scenario´.Select a script out of the list of Scripts
already available. Selected Scripts appear in the Scenario pane. Alternatively we can click the
³Browse´ button & navigate to the desired script ( for example: say basic_script) lying in our
known directory.
Step ± 3: Adding a script to the load test:

For the sake of illustration here we shall use just one Vuser script describing a single group of
users performing identical actions. Whereas in case of real world scenario involving variety of
user profiles, we can create different groups running several scripts with different user settings.

Step ± 4: Defining the group attri utes for the script:

a) Locate the desired script: Navigate to find out that that our desired script (basic_script in this
case) appears in the Group Name column of the Scenario Groups pane.

) Change Scenario group name: Select the script and click the ³Details´ button to launch the
³Group Information´ dialog box. Provide easily understandable enter a more meaningful name,
for example travel_agent.

c) Vusers Quantity: Provide the desired number of Vusers intended to be created in the group.

Click ³u´ to display the name in the Scenario Groups pane under the Design tab.

Step ± 5: Adding a load generator or localhost: for creating load on our application by running
the Vusers.

a) For using already availa le Load Generator: Click the ³Load Generators´ button In the
Design view to launch the ³Load Generators´ dialog box.

) For creating & using a new Load Generator: When the desired load generator does not
appear in the list, select ³Add´ from the Load Generator Name list to launch the ³Add New
Load Generator´ dialog box.

Provide the information like ³Name´ of the load generator and the type of ³Platform´ on which
the load generator is running. Click ³u´ to close the ³Add New Load Generator´ dialog box.

Involves instructing the Controller to make attempts to connect to the load generator machine.

a) Select ³localhost´ and click ³Connect´.

b) When the connection gets established, the status changes from ³Down´ to ³Ready´. Click
³Close´.

Step ± 6: Testing the Load Generator Connection:

Step ± 7: Scheduling of scenario in schedule pane of the Controller window:

In real world scenario, the actual users do not log on and off the system exactly at the same time.
Here we instruct the LoadRunner users to gradually log on to and off the system by scheduling
the scenario.
Select ³Scenario´ radio button under ³Schedule y´ and select ³Real-life schedule´ radio
button under ³Run Mode´, in the ³Scenario schedule´ Dialog Box;

Step ± 8: Setting the schedule actions definitions in Actions Grid:

In the Global Schedule Actions Grid four definitions are set.

We need to Double-click on every action in the first column like 1) Initialize 2) Start Vusers 3)
Duration 4) End Vusers, one by one in the above Action grid to launch the respective dialog
Boxes for defining the settings.

Step ± 9: Initializing of Vusers ± for getting ready for the load test run by running the vuser_init
action in the script & readying the load generators.

Double-click ³Initialize´ in the Action grid to launch the ³Edit Action´ dialog box. For this
tutorial, select the radio button of ³Initialize all Vusers simultaneously´.

Step ± 10: Starting of Vusers at specified Intervals: Double-click ³Start Vusers´ in the Action
grid to launch the ³Edit Action´ dialog box.

For this tutorial, feed 8 Vusers in the Start Vusers box, and select the second option box & feed 2
Vusers every 30 seconds.

Step ± 11: Specifying a duration: Through ³Interactive Schedule Graph´ a duration is

defined so that the Vusers keep on doing the scheduled action for a specific period thereby
enabling us to measure the continuous load on the server.

During the specified duration, the script will keep on doing as much iterations as possible
irrespective of the number of iterations defined in the script¶s run-time settings.

Click the ³Duration´ in the Action grid or click the horizontal line representing the duration in
the graph. The time line gets highlighted and a dot and a diamond appear at its endpoints. Drag
the diamond shaped endpoint to set the desired time say 00:11:30. This means that Vusers shall
run for a duration of 10 minutes.

Step ± 12: Stopping of Vusers - is done gradually.

Double-click ³Stop Vusers´ in the Action grid to launch the ³Edit Action´ dialog box.

For this tutorial, select the second option box & feed 2 Vusers every 30 seconds.

Step ± 13: Configuring the Run-time settings: to define the behavior of the Vusers during the
test.
Click the ³Run -Time Settings´ button in the ³Design´ tab. Then select the desired script and
modify the following run-time settings if necessary.

a) Run Logic to define the number of times a user repeats a group of actions.

b) Pacing to define the time to wait before repeating an action.

c) Log to define the type of information needed to be captured during the test.

d) Think Time to define the time a user stops to think between steps.

e) Speed Simulation to define network connections like modem, DSL or cable.

f) Browser Emulation to define different browsers.

g) Content Check for automatically detecting user-defined errors.

Step ± 14: Ena ling think time ± Select the ³General:Think Time´ node. Select ³Replay
think time´ radio button, and select the ³Use random percentage of recorded think time´
radio button. For this tutorial, specify a minimum of 50% and a maximum of 150%.

Step ± 15: Ena ling the logging option- Select the ³General:Log´ node. Select ³Enable
logging´ check Box. In the Log options, select ³Always send messages´. Select ³Extended
log´ radio button, and select ³Data returned y server´ check box for this tutorial.

Click ³OK´ to close the Run -Time settings dialog Box.

Step ± 16: Configuring the Windows Resources monitor: To view the performance of every
single tier, server and component of the application during the load test in real time.

a) upening of the Run view - by clicking the ³Run´ tab in the Controller window to display the
Windows Resources graph which is one of four default graphs getting displayed in the graph
viewing area.

Right-click the ³Windows Resources graph´ and select Add Measurements to open the
Windows Resources dialog box.

) Selection of monitored server ± Click ³Add´ In the Monitored Server Machines section of
the Windows Resources dialog box to open the ³Add Machine´ dialog box.

Type ³localhost´ in the ³Name´ field & specify the Name of the Platform say Win 2000 in the
³Platform´ field. Click ³u´ to close the ³Add Machine´ dialog box.

c) Activation of the monitor ± by clicking ³u´ in the Windows Resources dialog box.
With these steps the design of our Scenario gets complete & ecomes ready for the load
testing.