0% found this document useful (0 votes)
46 views

Performance Testing Using Jmeter

Uploaded by

anhlevanvcc
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
46 views

Performance Testing Using Jmeter

Uploaded by

anhlevanvcc
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Performance Testing Using

Presented by: Bùi Hoàng Dương


Email: [email protected]
Skype: [email protected]
Mobile:094.295.1515
What is Performance testing ?

Performance testing is an non-functional testing


performed to determine how a system performs in terms of
responsiveness and stability under a particular workload. It
can also serve to investigate, measure, validate or verify
other quality attributes of the system, such as scalability,
reliability and resource usage

GOAL/OBJECTIVE IS TO FIND THE BOTTLE NECK IN THE


SYSTEM
Focus of Performance Testing

Performance testing measures the quality attributes of the system, such


as scalability, reliability and resource usage.
The focus of Performance testing:
 Speed/Response Time - Determines whether the application
responds
quickly.
 Scalability - Determines maximum user load the software application
can handle.
 Stability - Determines if the application is stable under varying loads
Why Performance Testing is Needed?

Performance testing uncovers what needs to be improved before the


product goes to market. Without performance testing, software is likely
to suffer from issues such as:
 Running slow while several users use it simultaneously,
 Inconsistencies across different operating systems and poor
usability.
 Bottlenecks are obstructions in system which degrade overall
system performance. Some common performance bottlenecks are:
• CPU utilization
• Memory utilization
• Network utilization
Types of Performance Testing

Load testing - Applying desired number of load and checking the stability &
response time of the application.
Stress testing - Applying more then desired number of load and checking the
stability & response time of the application.
Soak/Endurance testing - To make sure the software can handle the expected
load over a long period of time.
Spike testing - by increasing the number of users suddenly by a very large
amount and measuring the performance of the system.
Volume testing - Transferring Huge volume of date & monitor the stability &
response time of the application.
Scalability testing - determines or validates whether adding another Y
resource (database, memory, disk, CPU, etc) increases speed of X proportionally
About JMeter

 It is an open source tool.


 It can load & perform test many different server types:
• Web – HTTP,HTTPS
• SOAP
• Database – JDBC
• LDAP
• JMS
• Mail – POP3(s) and IMAP(s)
 It allows concurrent sampling by many thread groups
 Test results can be captured in various format like
summary report, graph, results in tree & table, etc.
JMeter Work Flow
Pre-testing Activities
Design Review

The cheapest performance issues to address are ones that are never put into the
code.

Testers should review the application design to see if there are any
obvious potential performance problems.
Environment Prep - Network

Performance testing is often a network intensive activity which can affect


others in the organization

Testing should be done on a separate, segregated network.


Environment Prep - Hardware

Depending on what your goals are for your testing, different hardware is
appropriate for both the AUT and load generators.

Testers should acquire and configure the correct hardware.


Environment Prep - Software

Generating load is not as easy as it sounds.

Testers should acquire or create load generators and configure


them for their desired goal
Mission

Performance testing without a Mission is just throwing load at a server to


see what is going to happen.

Testers should determine Why they are doing their testing.


NFR document should be available – It will provide you the expected
Response time and required Concurrent user load, Scenarios to be tested
and other performance attributes.
Audience

Determining who you are generating numbers for, will largely dictate what
you do
• Development
• Marketing
• Operations
Metrics

Performance testing is all about numbers and metrics.

Testers should determine which metrics they are concerned about and how
to get them.
Give Warning

Let anyone who might be affected by your testing advance warning.

You might also like