You are on page 1of 41

n e r : A t a G l a n c e


Praveena Kumar
Why do we need testing?

Software has grown in complexity and size.

Software developed by a developer is according to the System Requirement

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.

Praveena Kumar Penkey

Additional reasons

• 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 don’t know what is needed or customers

have erroneous expectations

• Poorly documented code- requirement changes not updated in the source

Praveena Kumar Penkey
Limitation of Manual Testing

• Time consuming
• Low reliability
• Human resources
• Inconsistent

Automated Testing

• Speed
• Repeatability
• Programming
• Capabilities
• Coverage
• Reliability
• Reusability
Praveena Kumar Penkey
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

Praveena Kumar Penkey

What : LoadRunner ?

• is an automation tool

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

different peak loads.

Praveena Kumar Penkey

When to do load Testing?
•Single user testing primarily on functionality and user interface of a system

•Application testing focuses on performance and reliability of an entire system.

A typical application-testing scenario might depict 1000 users logging in
simultaneously to a system. This gives rise to issues such as what is the
response time of the system, does it crash, will it go with different software
applications and platforms, can it hold so many hundreds and thousands of
users, etc.

Praveena Kumar Penkey

Generate the Single user Script Load Test Procedure

Create Scenario

Generate Maximum Load (No. of

Users) / Scenario

Run the Scenario

Get the Results and Analyze

the Results

Praveena Kumar Penkey

Load Runner

VuGen Controller Analysis

1. Manual Scenario • Monitors

• Create Single User Script
• Metrics
• Insert: Transaction Points 2. Goal Oriented Scenario
Controlled Load Bottlenecks
Enhance Script : Maximum Load
•Parameterization Ramp up & Down
Rendezvous Point
Praveena Kumar Penkey
SLA & Resources
Select New Vuser Script / (if existing Open Existing
Open VuGen Script)

Praveena Kumar Penkey

Select proper protocol

Praveena Kumar Penkey

Record the script (Ctrl+R)

Give URL of “Application”

Set proper Action

Observe the events

Set Options

Praveena Kumar Penkey

Recording options

For “Correlation” in
“Web protocol”
Select “HTML-based”

Praveena Kumar Penkey

Depending on
Set proxy if ? “Application”

Praveena Kumar Penkey

Advanced Advanced
Check the boxes
Necessary options

Praveena Kumar Penkey

For Correlation:
Check the box

Praveena Kumar Penkey

Record Scenarios in “Action”
Observe the “Events”

Praveena Kumar Penkey

End Transaction

Set Transaction

Transaction’s in script

Praveena Kumar Penkey

End recording Stop Recording
selection “Vuser_end”

Praveena Kumar Penkey

Overview of VuGen Start & End
Transaction Points

Script View

Action View

Praveena Kumar Penkey
Enhance the script: Select the “String”
Once the script is ready go for parameterization
for “Parameterization”

Praveena Kumar Penkey

Select type and value

Praveena Kumar Penkey

Press ”properties” &
Set parameter type and
File path

Praveena Kumar Penkey

Simulate parameter
Enter values and simulate behaviors

Praveena Kumar Penkey

Format the
parameterization value

Praveena Kumar Penkey

Select row Update Value
• Sequential •Each Occurrence
• Random • Each iteration
• Unique •Once

Praveena Kumar Penkey

Observe parameterization

Praveena Kumar Penkey

Runtime setting (F4) before Run-time Settings  Pacing
Run(F5) the script

Praveena Kumar Penkey

Run-time Settings  Log Run-time Settings 
Think Time
(Depending on requirement)

For “Correlation” Check “Enable Logging” 

Check “Extended log” Check All Options

Praveena Kumar Penkey

Run-time Settings  Run-time Settings 
Miscellaneous. Speed Simulator.
“Process” consume
memory than “thread”

Praveena Kumar Penkey

F4 Browser Emulation.
Check cache details

Depending on

Praveena Kumar Penkey

F4 Proxy
F4 Preferences Options

Praveena Kumar Penkey

Set time out settings
(Change from 120 to 999sec)

Praveena Kumar Penkey

Before going to “ Correlation”
Run (F5) the script at least Please select “Log” in “Run
time Settings”
once for correlation


Correlation: The run time values generated by the server.

Praveena Kumar Penkey
Two kinds of “Correlation” exists

1. Automatic Correlation
2. Manual Correlation

Over view of “Correlation”

“Scan for Correlation”

or “Ctrl+F8”

Praveena Kumar Penkey

Automatic Correlation: Create Rule for “Correlation”

Before Recording
“Select Correlation

Praveena Kumar Penkey

While recording the Script After recording and
the Pop-up will come running the script, the
Rule is Created and
double click on it.

Praveena Kumar Penkey

Correlation Rule

Praveena Kumar Penkey

In Manual Correlation,
record two scripts
for same transaction
and compare the
scripts in
“Tools Compare
the Vuser”.
it opens “Wdiff”
Find the “Yellow lines“
for correlation
the dynamic data to be

Praveena Kumar Penkey

Observe the “Left,
Right boundary”

For manual “Correlation”

Insert the function
before “web_submit_data”

Praveena Kumar Penkey


Praveena Kumar Penkey