Performance testing is the process of determining the responsiveness, speed and stability of a software, network, computer program or device under a workload. Performance testing can involve quantitative tests done in a lab, or occur in the production environment with limited scenarios.
What is Performance Testing?
Testing the stability and response time of an application by applying load is known as performance testing. The document or requirement which speaks about the performance of an application we called as baseline document.
Performance testing is also known as spike testing, bottleneck testing, baseline testing, benchmark testing or breakpoint testing.
What is stability?
The ability to withstand the designed number of users is called stability. Eg: Customer will tell that application should be used by 10,000 people checking for 10,000 people and make sure application is stable for 10,000 users.
What is Response Time?
Time taken to send the request to the server, run the program which is requested by the user and receive response from the server is called response time.
Eg: Customer says when user tries to login home page should be displayed within 1 sec. Testing the above given statement to check if the home page is displayed in 1 sec or not is nothing but checking the response time.
What is Load?
Designed number of user is known as load. Eg: Customer says when 10,000 users use the application and try to login to application the home page should be displayed within 1 sec.
Testing the above statement is known as performance testing.
Response Time = T1+T2+T3
T1: Time taken to send the request for the server.
T2: Time taken to run the requested program in the server.
T3: Time taken to receive the request from the server.
Type of Performance Testing ?
1. Load Testing
2. Stress Testing
3. Scalability Testing
4. Volume Testing
5. Soak Testing or Endurance Testing
Load Testing
Testing stability and response time of an application by applying load which is less than or equal to designed number of users is called as load testing.
Eg: Requirement-> 10,000 users-> 1 sec Response time
1000- 0.5 sec
3000- 0.5 sec
5000- 1 sec
8000- 1 sec
10000- 1 sec
Stress Testing
Testing stability and response time of an application by applying load which is more than designed number of users is known as stress testing.
Eg: Requirement-> 10,000 users-> 1 sec Response time
11000- 1 sec
13000- 3 sec
15000- 8 sec
18000- 45 sec
20000- 1 min
Scalability Testing
Testing stability and response time of an application by applying load which is more than designed number of users and we exactly try to find the breakpoint where software crashes is known as scalability testing.
Eg: Requirement-> 10,000 users-> 1 sec Response time
21000- 2 min
23000- 4.5 min
30000- 10 min
45000- page not reachable or 404 error (Crash)
Volume Testing
Testing the stability and response time of an application by transfering huge volume of data is called volume testing. Here we mainly check the capacity of the Database.
Soak Testing or Endurance Testing
Testing stability and response time of an application by applying load continuously for particular period of time is called as soak testing.
Types of performance testing tool in market: Jmeter,Load runner, QA load, Neo load, Rational performance test.
This is an example of how to do performance testing using tool. Let's take Jmeter
1. Click on start recording.
2. It will start recording each and every action what user does.
3. Open the browser enter url login to application.
4. Now click on end recording.
5. Now specify url and the users to which performance testing should be done.
6. Tool will automatically convert action done by the user into code.
7. Now click on run button after few minutes you will get the result.
8. click on stop.
9. Now check start time and end time.
ConversionConversion EmoticonEmoticon