One of the most common questions in load testing is how to create a good test report that you would be able to present to your manager or customer. This big question actually consists of many smaller ones. What to start with? How to create the right test? What load parameters should be applied? How to interpret the results? Which numbers to look at when you browse through a long report generated by a load testing tool?
I will hardly answer all these questions and present the complete methodology in one article. This would be a long story and… it would be too boring. I know that there is a 90% chance that you really need something more simple and ready to use right away. I will simply present an example of the load testing report. A typical one, if you want.
However first of all I have to mention several steps you need to do in order to obtain the test data that you will use to create the report.
Now I am ready to show what I promised from the very beginning: an example of the load testing report. Please note that it is not a general template that can be used for all cases. It is rather a simple, but most common example. Here it is.
We need to find out if the web site meets the performance requirements as specified below.
The site needs to be able to handle 20000 unique visitors per day providing the industry standard level of service in terms of response time and error rate. Average response time should be less than 5 seconds and error rate should be less than 1%.
We also expect that average number of simultaneous users on site will be about 150, during the peak hours it will grow to 300. We need to check that the site can handle this load.
The following test conditions are most appropriate to simulate the real life site usage.
a) browse site content, perform search (80% of all users);
b) purchase items (20% of all users).
The following two tests have been designed and executed.
Test duration: 1 hour;
Load type: ramp-up from 10 to 300 users with step 30, every 5 minutes.
Test duration: 10 min;
Load type: ramp-up from 0 to 1000 users with step 2 every 1 second.
The performed capacity test has shown that the site preserves the desired quality of service only with a limited load. When the number of users simultaneously working with the site goes beyond 160, average response time starts to grow proportionally. When the number of users is about 300, the average response time increases to 19 seconds. See the graph below.
Number of active users
Maximum server productivity in terms of pages per second: 5,5 (see table below).
Pages per second
Maximum server productivity in terms of hits per second: 115 (see table below).
Hits per second
Server utilization %
The performed stress test has shown that when the number of users reaches 340, the server starts producing errors. The error rates increases with further load growth. See the graph and tables below.
Number of active users
Total errors %
The web site can experience slowdowns showing inacceptable response time in peak hours. When the load is at an average or below average level, the desired level of service is provided.
The web server resource utilization measured during the testing shows that the performance problems cannot be related to the web server hardware. We recommend to check if the database server resources are sufficient and/or increase the number of connections with the database.