load runner presentation.pps

8/14/2019 Load Runner Presentation.pps

1/70

Mercury InteractivesLoad Runner

Prepared byRavi Kumar AlampalliPresented by


2/70

11/1/2013 Wipro Confidential 2

What is Load Testing?

Testing an application under heavyloads, such as testing of a web siteunder a range of loads to determineat what point the system's responsetime degrades or fails.


3/70


Limitations of Manual Performance

Testing

Traditional or manual testing methods offer onlya partial solution to load testing.

Following are the drawbacks of Traditional Manual

Performance Testing:

1. It is expensive, requiring large amounts of bothpersonnel and machinery.

2. It is complicated, especially coordinating andsynchronizing multiple testers.

3. It involves high degree of organization, especiallyto record and analyze the results meaningfully.

4. Repeatability of the manual tests is limited.


4/70


What is LoadRunner ?

Mercury Interactives tool for testing the Performance ofApplication.

Reduces the personnel requirements by replacing humanusers with Vusers or Virtual Users.

Reduces Hardware Requirement because of numerous Vusers

can run on single machine. Enables you to test your system under controlled and peakload conditions.

LoadRunner Controller allows you to easily and effectivelycontrol all the Vusers from a single point of control.

Monitors the application performance online, enabling you tofine-tune your system during test execution.

Generates reports and graphs that provide the informationneeded to evaluate the performance of your application. Stresses your application to isolate and identify potential

client, network and server bottlenecks.


5/70


Components of LoadRunner

VuGen Generates Vuser scripts

LR Controller Creates and Runs LRScenarios

LR Analysis Used to Analyze theLoad test results.


6/70


How LoadRunner Works ?


7/70


LoadRunner Testing Process

Planning the Test

Creating Vuser Scripts

Monitoring the scenario

Creating the Scenario

Running the scenario

Analyzing the test results


8/70


Step I: Planning The Load Test

Load test planning process is a 3step process

Analyze the application

Define Load TestObjectives

Plan LoadRunnerImplementation


9/70


Analyzing the Application

Identifying System Components.

Describing the System

Configuration. Analyzing the Usage Model.

Task Distribution.


10/70


Defining Testing Objectives

Stating Objectives in MeasurableTerms.

Deciding When to Test.


11/70


Planning LoadRunnerImplementation

Defining the Scope of PerformanceMeasurements

Measuring end-to-end response time. Measuring network and server response

times.

Measuring GUI response time.

Measuring Server response time. Measuring middleware-to-server response

time.


12/70


Examining Load TestingObjectives

Your test plan should be based on a clearlydefined testing objective.This section presents an overview of commontesting objectives:

Measuring end-user response time Defining optimal hardware configuration Checking reliability Checking hardware or software upgrades

Evaluating new products Identifying bottlenecks Measuring system capacity


13/70


Day 2

VuGen

Virtual User Generator


14/70


Step II: Creating Vuser Scripts

LoadRunner replaces human users with virtualuser or Vuser.

Vusers emulate the actions of human users by

performing typical business processes. Eachaction that a Vuser performs submits input to theclient/server system.

To emulate condition of heavy user load, you

create a large number of Vusers that perform aseries of task. The actions that are performedduring a scenario are described in a Vuser script.


15/70


16/70


Virtual User Generator -

VuGen

LoadRunners Primary tool fordeveloping Vuser scripts is knownas Vuser Script Generator, alsoknown as VuGen.

VuGen not only records Vuser

Scripts, but also runs them.


17/70


Virtual User Generator -

VuGen

VuGen is used to:

Monitor the communication betweenthe application and the server,

Generate the required functionalcalls

Insert the generated function callsinto a Vuser script.


18/70


Step a: Recording Vuser Scripts with

VuGen

VuGen Creates a Vuser script byrecording the communicationbetween a client application and

server.Each Vuser Script that you createcontains at least 3 sections:

vuser_init

one or moreActions

vuser_end


19/70



VuGen

TO Create a new VuserScript:

1. SelectStart ->Programs->

LoadRunner->Virtual User Generator

Then VuGen MainWindow opens.

2. Select File -> New or Clickon NewButton then thefollowing screen will bedisplayed.


20/70



VuGen

3. Select the desiredProtocol from theProtocol Type list.

For eg:- selectHTTP Protocolfrom the list andclick on OK then

the Protocol dialogbox closes.


21/70



VuGen

4.Now Click on the

Recordbutton( RedCircle Button).

Following screen will be

displayed.

5.Enter the values forthe URL and Record intoaction and click on OK.

The dialog box closed

and begin recording.


22/70



VuGen

6.When you reach thepoint at which youwant to startrecording, clickRecord. If you decide

not to record clickabort.7.VuGen Starts yourapplication and therecording tool barappears.

8.Click on the BlackSquare button (Stopbutton) to stop therecording the actions.


23/70



VuGen

9.Once recordingis done the scriptview screen is

displayed.


24/70


Step b: Enhancing the Vuser Script

Sometimes we may face thesituation that we may require toenhance the Vuser scripts. You canenhance the scripts by addingfollowing type of functions.

General Vuser functions

Protocol-Specific Functions

Standard ANSI C-Functions


25/70


Step b: Enhancing the Vuser Script

Transactions:- Measures the time takesfor the server to respond to specifiedVuser requests.

To measure a transaction, you insertVuser functions to mark the beginningand end of the transaction. In a script you

can have as many transactions you wantwith a different name.


26/70


Inserting Transactions into a Vuser

Script Start Transaction

To start the Transaction

1.While recording the scriptclick on the starttransactionbutton of therecording tool bar.

2.Start Transaction dialogbox opens.

3.Enter the transaction nameand click on OK.

4.VuGen insertslr_start_transaction(); intothe Vuser scripts whichindicates the start of thetransaction.


27/70


Inserting Transactions into a Vuser

Script End Transaction

To End the transaction1.While recording the scriptClick on the EndTransactionbutton.2.End Transaction Dialogopens.3.Enter the transactionname and transactionstatus that need to be endand Click on OK.4. VuGen insertslr_end_transaction(,LR_AUTO);into the Vuser scripts whichindicates the start of thetransaction


28/70


Inserting a Rendezvous Point

To emulate heavy user load on yourclient/server system, you synchronizeusers to perform a task at exactly the

same moment. You ensure that multiplevusers act simultaneously by creating arendezvous point. When a vuser arrivesat the rendezvous point, Vuser is held by

the controller until all the Vusersparticipate in the rendezvous.


29/70


Inserting a Rendezvous Point

To Insert a Rendezvous Point

1.While recording a Vuserscript Click theRendezvous button on theRecording toolbar.Rendezvous dialog opens.

2.Enter the RendezvousName and click on OK.

3.VuGen inserts anlr_rendezvous(); to theVuser script.

Note:-You can not addRendezvous point toVuser_init and Vuser_endaction of your script.


30/70


Inserting a Comment

To Insert a Comment

1.While recording a Vuserscript Click the Commentbutton on the Recordingtoolbar. Rendezvous dialogopens.

2.Enter the Comment andclick on OK.

3.VuGen inserts thefollowing lines to the code

/*

* Comment**/


31/70


Parameterizing the script

VuGen generates a script thatcontains the actual values usedduring recording. Suppose you wantto perform the scripts action usingdifferent values from thoserecorded. To do this, you replace

the recorded values withparameters. This is known asparameterizingthe script.


32/70



Advantages of the Vuser script.

It reduces the size of the script.

It provides the ability to test your script withdifferent values.

Parameterization involves 2 tasks

Replacing the constant values with the vuserscript with parameters.

Setting the properties and data source for theparameters.


33/70



Let us say that VuGen generated thefollowing statement

Web_submit_form(db2net.exe,ITEMDATA,name=library .Title,value=XYZ,ENDITEM);

When you replay the script with

multiple vusers and iterations youdont want to repeatedly use the samevalue for the Value XYZ then you canreplace the constant value with aparameter. This can be done in thefollowing way.

1.Select the value XYZ and right clickthe mouse

2.select replace with a parameteroption

3.Following screen will be displayed.4.Enter the value for the parametername

and click on OK.5.Vuser script will changed as following.

Web_submit_form(db2net.exe,ITEMDATA,name=library .Title,value={Book_Title},ENDITEM);


34/70


Defining Parameter Properties

1. Right Click the parameter andright click pop-up opens.

2. From the Pop-up menu, selectparameter properties. Theparameter properties dialog boxopens and displays the

properties that are relevant forthe current parameter type.

3. Change the Propertiesaccordingly and click on Close.


35/70


Step C: Configuring Runtime Settings

After you record a vuser script, you can

configure its run-time settings. The run-time settings define the way that the script

runs. These settings are stored in the filedefault.cfg, located in the vuser scriptdirectory. Run-time settings are applied tovusers when you run a script using VuGenor controller.


36/70


Displaying Runtime settings Dialog

Click on the Run-TimeSettings button on theVuGen Tool bar.

Press the keyboard

shortcut key F4. Choose Vuser->Run-

Time settings.


37/70


Configuring the Pacing Run-Time

settings

Click on the Run-timesettings button of thetool bar.

Click on the Pacing Tab

Pacing Tab of the Run-time settings dialogopens.

Here you can set theNo. of Iterations in theIteration Count box

and also select theoptions for executingthe next iteration.


38/70


Configuring Actions.

When you run scripts with multipleactions, you can indicate how toexecute the actions and you canconfigure the way a vuser executesactions.


39/70


Configuring Actions.

Action Blocks:- Action blocks are groups of actionswithin your script. You can set the properties ofeach block independently its sequence,weighting and iterations.

Sequence:- order of actions within your script is

known as a sequence. This can be a sequentialorder or random order.

Weighting:- When working in random mode, you canset the number of times a particular action isexecuted in relation to another. This is expressedin %.

Iterations:- you can set the No.Of iterations not onlyfor the entire Run action but also for individualactions or action blocks.


40/70


Creating Action Blocks

1. In the pacing tab, right-click the word Runin thetree view and chooseInsert Action Block.

2. Add Actions to the block.You can only add actions

that exists and aredisplayed in the actionssection.

3. Right click the word blockand chooseInsert IntoBlock > Actions. Theselect actions list opens.

4. Select an action to add tothe block and click Ok.


41/70


Changing the sequential order of

blocks or actions

In the pacing treeview, select the itemyou want to move andperform a right click.

A menu opens Choose Move Item up

or Move item down tomodify the itemsposition.

Repeat the abovesteps to move ananother item.


42/70


Run items randomly

In the iterations tab treeview, right click the itemwhose elements you wantto randomly execute. If youwant to set blocks oractions that reside directly

in the Run section, selectthe word Run. If you to setthe random mode foractions within a block,select the block number. Amenu opens.

Choose theproperties.Run properties dialog opens

Select Random from RUNLogicList

Click on OK


43/70


Setting action Weighting

When you run actions randomly,you can indicate the rate at whichloadrunner executes each action. Bydefault, loadrunner assigns an equalweighting to all the actions.

To set the weighting of blocks oractions:

1. Make sure that the run logic for theitem you want to set is Random( Ifa percentage appears next to theitem, it is in random mode).

2. Right click the item whosepercentage you want to change, andchoose properties. The action

properties dialog opens.

3. Specify the desired percent andclick on OK


44/70


Configuring the Log Run-Time settings

During execution, vusers loginformation about themselves and theircommunication with the server. Inwindows environment this informationis stored in a file called output.txt

Click on the Run-Time settings buttonor select vuser->Run-time settings todisplay the Run-time settings dialogbox.

Click on the Log tab to display the logoptions.

To enable logging during replay, Checkthe check box Enable Loggingother wise deselect this check box.

2 types of Log options are there Send messages only when an

error occurs Always send messages.

2 levels of log details are there Standard Log Extended Log


45/70


Configuring the Think Time settings

Vuser think time emulates the time that a realuser waits between actions.

For eg:-when a user receives data from aserver, the user may wait several seconds toreview the data before responding. This delayis known as think time. VuGen useslr_think_timefunctions to record think timevalues into your Vuser scripts.

Configuring the think time:

Click on the run-time settings button on theVuGen tool bar

Click on the think time tab to display the thinktime options.

You ignore the think time or replay the thinktime and the following options are available forreplay think time.

As Recorded:- this option is used to replaythe script with the recorded think time.

Multiply recorded think time by: during

replay it multiplies the recorded think time byspecified factor. Use Random percentage of the recorded

think time: uses a random % of recordedthink time for a given range

Limit think time: Limits to maximum value


46/70


Configuring the General Run-Time

settings

We can set the followinggeneral run-time optionsfor a vuser script:

Error handling Multithreading Automatic Transactions

Configuring the GeneralRun-Time settings:

Click on the Run-time

settings button.

Click on the General tab todisplay the general options.


47/70


Step d: Running the Vuser scripts in

stand alone Mode

After developing a vuser script, run it using theVuGen to ensure that it executes correctly.

You can run vuser script in following modes:

Animated Mode :- Highlights the line that is beingexecuted.

non-animated mode:- Do not highlight the line

that is being executed.


48/70


Step E: Incorporating the vuser script

into a scenario

Once you have successfully run a script in stand-alone mode to verify that it is functional, youincorporate the script into a scenario. A scenariocontains the information about the:

Vuser that will run the script Load generator upon which the script will be

executed.

You can also create a simple scenario from VuGenthat uses the current vuser script


49/70


Incorporating the vuser script into a

scenario

To create a scenario from VuGen:

Choose tools>Create ControllerScenario. Create scenario dialog boxopens.

Choose either goal oriented ormanual scenario.

For manual scenario enter the No.of Vusers you want to execute thescript.

Enter the name of the machine,group name upon which you wantthe vusers to run for manualscenario.

Enter the script name for the goal

oriented scenario Enter the result directory

Click on OK to add the script to thecurrent scenario.


50/70


Day 3

Load Runner Controller


51/70


Step III: Creating a Scenario

Scenario:-A scenario defines the events thatoccur during each testing session. For e.g.:- ascenario defines and controls the number ofusers to emulate, the actions that they perform,

and the machines on which they run theiremulations.

There are 2 methods of creating a scenario:

Manual Scenario. Goal-Oriented Scenario.


52/70


Manual & Goal Oriented Scenario

Manual Scenario:-In Manual Scenario,you create the scenario yourself bydefining the number of Vuser groups you

want to run and building a schedule forthe LoadRunner to run these groups.

Goal Oriented Scenario:-In Goal Orientedscenario, you define the goals you want

your test to achieve and LoadRunnerautomatically builds a scenario for youbased on these goals.


53/70


Creating a Manual Scenario

1.Click on Start ->Programs->LoadRunner ->Controller

Controller Opens2.Click on the New

Scenario button, New

Scenario dialog openswith the list of VuserScripts and select thedefault option ManualScenario for scenariotypes.

3.Select the requiredscript/scripts byclicking on theAddbutton.

4.Click on Okto add thescript to the scenario.


54/70



5.Scenario Group screenwill be displayed.

6.Enter the No. Of Vusersin the QuantityColumn.

7.Enter the ipaddress orthe machine name of thesystem underloadgeneratorcolumn.

8.Click on Add groupbutton to add anothergroup to the scenario,Add group dialog opensand repeat the abovesteps.


55/70



Percentage Mode

1.Click on Start ->Programs->LoadRunner ->Controller

Controller Opens2.Click on the New

Scenario button, New

Scenario dialog openswith the list of VuserScripts.

3.Select the ManualScenario option andalso the check thecheck box User thepercentage option..

4.Select the required

script/scripts byclicking on theAddbutton.

5.Click on Okto add thescript to the scenario


56/70



Percentage Mode.

6.Scenario Group screen willbe displayed.

7.Enter the No. Of Vusers inthe Total No. Of Vusersfield.

8.Enter the ipaddress or the

machine name of thesystem underloadgeneratorcolumn.

9.Enter the percentage in the%field.

10.Click on Add group buttonto add another group to the

scenario, Add group dialogopens and repeat theabove steps.


57/70


Creating a Goal Oriented Scenario

In Goal-Oriented scenario, you define the goalyou want your test to achieve, and LoadRunnerautomatically builds a scenario for you, based onthese goals.

There are 5 types of Goals:

1. Number of Vusers

2. Number of Hits per second (Web Vusers only)

3. Number of Transactions per second.4. Number of Pages per minute (Web Vusers only)

5. Transaction response time.


58/70



Virtual Users:-

If you want to test how many Vusers your application can runsimultaneously, you define a Vuser goal type.

Pages per minute/Hits per second/Transactions per second:-

If you want to test the strength of your server, it is recommendedthat you define Hits per second, Pages per minute or Transactionsper second goal type.

Transaction Response time:-

If you want to test how many Vusers can be run simultaneouslywithout exceeding a desired transaction response time, it isrecommended to define a Transaction Response time goal type.


59/70



1.Click on Start ->Programs->LoadRunner ->ControllerController Opens

2.Click on the NewScenariobutton, New Scenariodialog opens with the listof Vuser Scripts.

3.Select the Goal OrientedScenario option

4.Select the requiredscript/scripts by clicking

on theAdd button.5.Click on Okto add thescript to the scenario.


60/70



Define a scenario Goal.

1. Click on Edit scenario goalbutton. Edit scenario goaldialog box opens.

2. Select a goal profile name.To enter a new name, clickNewbutton to Rename aprofile, Click on RenameButton then Goal Profiledialog opens.


61/70



3. In the define scenario goal box, select a Goal Type.

Virtual Users:-

Enter a target number of Vusers that you would like your scenario to reach.

Hits per second:-

Enter target number of hits per second, and also enter minimum and maximum number

of vusers for the scenario.

Transactions per second:-

Enter a target number of transactions per second that you would like your scenario toreach.

Transaction Response Time:-

Enter a target transaction Response time and select minimum and maximum number ofvusers.

Pages per minute:-

Enter a target number of downloaded pages per minute and select minimum andmaximum number of vusers for the scenario.


62/70



4. In the scenario settings tab mention the time thescenario has to be executed after achieving the goal.

5.Choose whether you want to stop the scenario andsave the results or continue the scenario, if controllerdoes not succeed in reaching the target. Check thecheck box Receive notification if loadrunner fails.

6.Select the Load Behavior tab. If you have selectedthe transactions per second or Transaction responsetime goal type, choose whether you want loadrunnerto reach your target by automatically running a

default no. of users or certain period of time you wantto ramp up the load.


63/70


Step IV: Running a Scenario

Once the scenario is created we need to execute the

scenario.

This can be done by clicking on the Start Scenariobutton.

During scenario execution loadrunner:

Records the durations of the transactions you definedin the vuser scripts.

Performs the rendezvous included in the script. Collects the error, warning and notification messages

generated by the vusers.

Monitors each vuser


64/70


Step V: Monitoring a Scenario

During execution of a scenario you can monitor the scenarioexecution using the Loadrunner online monitors.

LoadRunner Provides the following online Monitors:

1. Run-Time Monitors

2. Transaction Monitors3. Web Resource Monitors4. System Resource Monitors5. Network Delay Monitors6. Firewall Monitors7. Web Server Resource Monitors8. Web Application Server Resource Monitors

9. Database Server Resource Monitors10. Streaming Media Monitors11. ERP Server Resource Monitors12. Java Performance Monitors


65/70


Step VI: Analyzing the Results.

Once the Scenario are executed and the results are stored,

results can be analyzed through the tool LoadRunnerAnalysis.

Steps to Open the results file in LR analysis:

1.Start->Programs-> Load Runner->Analysis

2.Click on the New Button.

3.Select the Results file.

4.Click on the graphs link in the left navigation bar.

5.You will see different graphs on the right hand side pane.


66/70



Once the Scenario are executed and the resultsare stored, results can be analyzed through thetool LoadRunner Analysis.

Steps to Open the results file in LR analysis

1.Start->Programs-> Load Runner->Analysis

2.Click on the New Button.

3.Select the Results file.

4.Click on the graphs link in the left navigationbar.

5.You will see different graphs on the right handside pane.


67/70



Following are the some of thegraphs that are generated by theLoadRunner.


68/70




69/70


References

To Know More about LoadRunner Refer the Following:

LoadRunner Vuser Generator Users Guide

LoadRunner Controller Users Guide.

LoadRunner Analysis Guide.

http://www.mercuryinteractive.com/products/loadrunner/

http://www.mercuryinteractive.com/products/testcenter/
http://www.mercuryinteractive.com/products/loadrunner/http://www.mercuryinteractive.com/products/testcenter/http://www.mercuryinteractive.com/products/testcenter/http://www.mercuryinteractive.com/products/loadrunner/


70/70

Thank You!

load runner presentation.pps

Documents