Seven methods of software performance testing

1. Benchmark testing

Benchmark testing refers to the quantitative and comparable testing of a certain index of a class of test objects through the design of scientific testing methods, testing tools and testing systems.

2. Stress test

By constantly applying pressure to the software system, the inflection point of system performance is identified, and the test activities of the larger service sector provided by the system are obtained. The main purpose is to check the performance of the system application under pressure.

3. Load test

The pressure is continuously increased in the system under test until the performance target limit is reached. The main purpose is to find the limits of the system's processing power in a particular environment.

4. Concurrent testing

It mainly refers to whether there are hidden concurrency problems when testing multiple users to access the same application, module, and data, such as memory leaks, thread locks, and resource contention problems. Almost all performance tests involve concurrency testing. The main purpose is not to obtain performance indicators, but to discover and cause problems.

5. Fatigue test

By letting the software run for a long time under a certain amount of traffic to check how long the system performance will significantly decline, the main purpose is to verify the reliability of the system operation.

6. Data volume test

Test system performance against various data volumes by having software run on different data volumes. The main purpose is to find the data volume permissions that support the proper functioning of the system.

7. Configure the test

Configuration testing is mainly for hardware, to understand the impact of different environments on system performance, so as to find the optimal allocation principle of system resources. The main purpose is to understand the extent to which different factors affect the system performance, so as to determine the more worthwhile tuning operations.