Performance Testing Using Jmeter
Performance Testing Using Jmeter
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
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
Depending on what your goals are for your testing, different hardware is
appropriate for both the AUT and load generators.
Determining who you are generating numbers for, will largely dictate what
you do
• Development
• Marketing
• Operations
Metrics
Testers should determine which metrics they are concerned about and how
to get them.
Give Warning