7283145 load runner atglance vugen

8/14/2019 7283145 Load Runner AtGlance Vugen

1/41

LoadRunner:AtaGlance

Praveena KumarPenkey


2/41

Praveena Kumar Penkey

Software has grown in complexity and size.

Software developed by a developer is according to the System Requirement

Specification.

An organization invests large sums in making a software product, it must

ensure that the software product must be acceptable to the end users.

This is where Testing comes into play. Testing is not merely finding

defects or bugs in the software, it is the completely dedicated discipline of

evaluating the quality of the software.

Why do we need testing?


3/41


Poor requirements if requirements are unclear, incomplete, too general, or

not testable

Unrealistic schedule too much work is crammed in too little time

Inadequate testing no one will know whether or not the program is any

good until the customer complains or systems crash

Requirements change requirements changes after development

Miscommunication developers dont know what is needed or customers

have erroneous expectations

Poorly documented code- requirement changes not updated in the source

code

Additional reasons


4/41


Limitation of Manual Testing

Time consuming Low reliability Human resources

Inconsistent

Automated Testing

Speed

Repeatability Programming Capabilities Coverage Reliability Reusability


5/41


Which Test Cases to Automate?

Tests that need to be run for every build of the application (sanity check,regression test) Tests that use multiple data values for the same actions (data driven tests)

Tests that require detailed information from application internals (e.g., SQL,GUI attributes) Stress/load testing

Which Test Cases not to Automate?

Usability testing One-time testing Ad hoc/random testing Tests without predictable results


6/41


What : LoadRunner ?

is an automation tool

to know the performance of the application in different environments and with

different peak loads.


7/41


When to do load Testing?

Single user testingprimarily on functionality and user interface of a systemcomponent.

Application testingfocuses on performance and reliability of an entire system.A typical application-testing scenario might depict 1000 users logging insimultaneously to a system. This gives rise to issues such as what is theresponse time of the system, does it crash, will it go with different softwareapplications and platforms, can it hold so many hundreds and thousands ofusers, etc.


8/41


Load Test ProcedureGenerate the Single user Script

Create Scenario

Generate Maximum Load (No. of

Users) / Scenario

Run the Scenario

Get the Results and Analyzethe Results


9/41


Load Runner

VuGen

Create Single User Script

Insert: Transaction Points

Enhance Script :

Parameterization

Correlation

Controller

1. Manual Scenario

2. Goal Oriented Scenario

Controlled Load

Maximum Load

Ramp up & Down

Rendezvous Point

SLA & Resources

Analysis

Monitors

Metrics

IdentifyBottlenecks


10/41


Open VuGen

Select New Vuser Script / (if existing Open Existing

Script)


11/41


Select proper protocol


12/41


Record the script (Ctrl+R)

Give URL of Application

Set proper Action

Set Options

Observe the events


13/41


Recording options

For Correlation in

Web protocol

Select HTML-based


14/41


Set proxy if ?Depending on

Application


15/41


AdvancedAdvancedcheck

Necessary optionsCheck the boxes


16/41


For Correlation:

Check the box


17/41


Record Scenarios in ActionObserve the Events


18/41


Set Transaction

End Transaction

Transactions in script


19/41


End recording

selection Vuser_endStop Recording

O i f V G St t & E d


20/41


Overview of VuGen Start & End

Transaction Points

Script View

Action View

Log

E h th i t


21/41


Enhance the script:

Once the script is ready go

for Parameterization

Select the String

for parameterization


22/41


Select type and value


23/41


Press properties &

Set parameter type and

File path


24/41


Enter values and simulateSimulate parameter

behaviors

Format the


25/41


Format the

parameterization value


26/41


Select row SequentialRandom Unique

Update ValueEach OccurrenceEach iterationOnce


27/41


Observe parameterization


28/41


Runtime setting(F4) before

Run(F5) the scriptRun-time SettingsPacing


29/41


Run-time Settings Log Run-time Settings Think Time

(Depending on requirement)

For Correlation Check Enable Logging Check Extended log Check All Options


30/41


Run-time Settings Miscellaneous.

Process consume

memory than thread

Run-time SettingsSpeed Simulator.


31/41


F4 Browser Emulation.Check cache details

Depending on

requirements


32/41


F4ProxyF4 Preferences Options


33/41


F4PreferencesOptions

Set time out settings

(Change from 120 to 999sec)

Before going to Correlation


34/41


Run (F5) the script at least

once forcorrelation

Correlation: The run time values generated by the server.

Before going to Correlation

Please select Log in Run

time Settings

Select

Two kinds of Correlation exists


35/41


1. Automatic Correlation

2. Manual Correlation

Over view of Correlation

Scan for Correlation

or Ctrl+F8


36/41


Before Recording

Select Correlation

Studio

AutomaticCorrelation: Create Rule for Correlation


37/41


While recording the Script

the Pop-up will come

After recording and

running the script, the

Rule is Created and

double click on it.


38/41


Correlation Rule


39/41


In Manual Correlation,

record two scripts

for same transactionand compare the

scripts in

Tools Comparethe Vuser.

it opens Wdiff

Find the Yellow linesfor correlation

the dynamic data to be

correlated.


40/41


For manual Correlation

Insert the function

web_reg_save_param

before web_submit_data

Observe the Left,

Right boundary


41/41

P K P k

Functions:

1.web_create_html_param()

2.web_create_htm_param_ex()3.web_reg_save_param()

4.web_set_max_html_param_len()

7283145 load runner atglance vugen

Documents