Performance test method

1、 Acceptance performance test

      Concept ： Simulate the production and online business environment （ Real environment 、 Current network environment ）, Test whether the performance requirements are met

      characteristic ：①、 Determine the user's environment ;②、 Performance indicators required by users ;③ perform 、 The results of the analysis ;④、 Nature of acceptance ;⑤ There must be objective results .

2、 The load test

      It mainly investigates the performance of the software system under the given load

      Understanding level ： It is a method of performance testing

      Concept ： Performance of software system under certain load

      emphasize ： Certain load -- Generally, it is the load required by customers

      This indicator is generally withdrawn ： response time 、 Trading capacity （TPS）、 Concurrent capacity 、 Resource utilization, etc ~

3、 Pressure test

      In order to investigate the performance of the system under extreme conditions , Extreme conditions can be overloaded transaction volume and concurrent users

Be careful ： This extreme condition is not the user's performance requirements , It may be much higher than the performance requirements of users

    The difference between load testing and stress testing

    The load test ： What we care about is user rules and requirements , Standards reached by the product

    Pressure test ： Concerned about the software system itself . And can give solutions

    When we are doing software stress testing , There are often more concurrent users and transactions than load testing .

    Pressure test ： The expected result is that the system has problems , What we want to examine is the way the system handles problems .

    for instance , We expect a system to remain stable under pressure , Processing speed can be slower , But the system cannot crash , therefore , Stress testing allows us to identify weaknesses in the system and how the program will run under extreme load .

4、 Concurrent test

     （ It refers to a very specific request ）

      Verify the concurrent processing capability of the system

      It usually establishes a large number of concurrent links with the server , Through the response time of the client and the performance monitoring of the server, we can judge whether the system has reached the established concurrency index .

5、 Configuration testing

By adjusting the software and hardware environment of the tested system , Understand the impact of various environments on equivalent performance , So as to find the optimal allocation principle of system resources .

Generally used for performance tuning and planning capabilities .

Hardware related products are all measured through configuration testing .

6、 Reliability test （ Stability test ）

      Test whether the system will have problems after running under a certain load for a long time

      Some problems of software system cannot be exposed at once , Or it takes time to accumulate to reach a measurable level .

    This problem is usually caused by the program occupying resources but not releasing them in time . such as , The memory leak problem will only become significant after a period of accumulation , It is difficult to check out at the beginning of operation .

    Link path between client and server , Can not be effectively released in time .

7、 Recovery testing

Designed for systems with redundant backup and load balancing . Used to detect if the system fails locally , Whether the user can continue to use the system , And if that happens , To what extent will users be affected .

Test whether the system can quickly recover from the error state to the normal state .

Main purpose ： Verify that in case of partial failure , Whether the system can continue to use . Generally, the key business system will be realized by hot backup or load balancing .

How many user accesses can be supported when a problem occurs .

Not all systems need to be tested for failure .

Defect discovery

Main purpose ： Find the defects in the system by means of performance test , There is no performance index to refer to or performance goal to be achieved , Therefore, the method of concurrent testing is used .

If you still need to pay attention to the problems in the process of pressure and failure recovery , Then the methods of stress test and failure recovery test can be used .

Performance benchmarking

Without setting clear performance goals , The performance changes in each train iteration are obtained through comparison , According to these changes, decide whether the iteration has achieved the expected goal .

Common methods ： Pressure test 、 Concurrent test .