design and developed by HP Load runner specialist

1. Faiz Muhammad
S.Q.A Manager
Accredited Integration Specialist
HP Performance Center v9
(creator)
Performance Testing
Load Testing
Stress Testing
Volume Testing

2. Performance Testing
• Performance tests are normally interested in
both “how much?” and “how fast?”
• This concludes all three:
– Load Testing
– Stress Testing
– Volume Testing

3. Load Testing
• focuses on “how much” can the application
handle.
• Measures the max limit of transactional load
that can be bear by application under test
• Holds the max limit permanently as far as the
given environment remain same.
• Example: A spring can bear load of 650KG

4. Stress Testing
• Load and activities are more “stressful” than the
application is expected to encounter. This may
include:
– Too many users
– Too much data
• Some sub categories are:
– Spike testing (Short burst of extreme load)
– Extreme load testing (load test with too many users)
– Hammer testing (hit it with everything you have got, but with no delays)
• Example: A spring will be in a stress after 660 KG.

5. Volume testing
• Any test focused on “how much” instead of
“how fast”
• Often related to database testing
• Does not focus on how much users
• Only focus on how much data

6. LoadRunner
• Previously known as Mercury Interactive
LoadRunner.
• After version 8.0 Mercury Interactive was sold
to HP.
• It’s a performance testing tool, and can do:
– Load testing
– Stress testing
– Volume testing

7. Architecture Overview

8. How LoadRunner Works