Load Testing
EchoAPI supports load testing in automated testing, enabling developers and testers to efficiently evaluate and optimize the performance of APIs (Application Programming Interfaces). Note: This feature is limited to the client experience.
Feature Introduction
Load Testing Modes
Currently, load testing supports two modes: Fixed and Ramp-up.
Fixed：Sets a fixed number of concurrent users, maintaining this fixed value throughout the load testing period.
Ramp-up：This mode includes an initial concurrency, the duration of the initial concurrency, a ramp-up interval (the range from initial concurrency to maximum concurrency), ramp-up duration, maximum concurrency, and maximum concurrency duration. It starts with a smaller concurrency and gradually increases to the maximum concurrency.
During Load Testing
After preparing the test cases (see how to prepare test cases) and configuring the load testing conditions, click Run or Save and Run to perform performance testing. Note: Only the reports generated by clicking Save and Run will be stored; reports generated by clicking Run will not be saved.
During the load testing process, various metrics such as the number of requests, failed requests, response time, average response time, etc., can be viewed in real-time. The details of failed requests will only be provided after the load testing has concluded.
It is not possible to close the drawer popup during the load testing process. Forcefully closing it will indicate that you do not wish to continue with the load testing.
Load Testing Report Interpretation
Overview & Performance details for total duration
| Metric | Meaning |
|---|---|
| Total Requests | Total Number of Requests Sent During Load Testing. Unit:(times) |
| Failed requests | Total Number of Failed Requests During Load Testing. Failure includes two cases: 1.HTTP status codes outside the 2xx range; 2.Assertion failures. If either condition is met, it counts as a failure. If both conditions are met, the error reason will be classified under "HTTP Status Code Not 2XX." |
| Failure rate | Failed Requests / Total Requests * 100% |
| Avg. Resp. Time(ms) | Average Response Time for Requests During Load Testing. |
| Min Resp. Time(ms) | Minimum Response Time for Requests During Load Testing |
| Max Resp. Time(ms) | Maximum Response Time for Requests During Load Testing |
| TPS | Total number of all executed interfaces during the load test / (Time of the last request - Time of the first request). Unit: (times/second) |
| Avg. Accepted Traffic | Average Incoming Traffic During Load Testing. |
| Requests /second | Total number of all executed interfaces during the load testing / Duration of the load testing. Unit: (times/second) |
| 90%(ms) | Sort all response time values in ascending order and take the value at the 90th percentile. For example, if 100 data points are collected and sorted from smallest to largest, the 90th data point will be used for statistics. This indicates that 90% of requests will be completed within this time frame. |
| 95%(ms) | Sort all response time values in ascending order and take the value at the 95th percentile. For example, if 100 data points are collected and sorted, the 95th data point will be used for statistics. This indicates that 95% of requests will be completed within this time frame. |
| 99%(ms) | Sort all response time values in ascending order and take the value at the 99th percentile. For example, if 100 data points are collected and sorted, the 99th data point will be used for statistics. This indicates that 99% of requests will be completed within this time frame. |
Performance Graph
A real-time trend chart reflecting dynamic changes in metrics during the load testing period.
TOP 5 Failure Causes
A summary of failure reasons during the load testing, highlighting the top 5 reasons with the highest occurrence.
Failure Distribution Graph
A trend chart showing the number of occurrences for each failure reason during the load testing period.
Failure Details
You can view which requests caused each failure. By clicking on the interface, you can see the specific request and response details.
