foreword
There are several types of performance testing. The common types are load testing and stress testing. Of course, concurrent testing is also a relatively common type, which are listed below.
PS: A mind map of performance test types is attached at the end of the article
1. Load test (placeability test)
Definition: Increasing stress on the system under test until performance metrics (such as response time) exceed expectations or some resource usage is saturated. The processing limit of the system can be found to provide data for system tuning
Features:
1): The main purpose of this method is to find the limit of the system processing capacity
2): This method is carried out in a given test environment, and usually needs to consider the business pressure and typical scenarios of the system under test
3): This method is generally used to understand the performance capacity of the system, or to use it with performance tuning
Performance capacity: how many concurrent users the system can allow while ensuring a certain response time
2. Stress test
Definition: When the system is in a certain saturated state, such as CPU, memory, etc., the session capacity that the system can handle, and whether the system will encounter errors
Features:
1) The main purpose of this method is to check the performance of the application when the system is under stress
This method maintains the usage of system resources at a certain level by increasing the access pressure, and checks the performance of the application at this time, focusing on the generation of error messages, the response time of the system to the application, etc.
2) This method generally uses methods such as simulated load to make the resource usage of the system reach a higher level
3. Acceptance performance test
Definition: To verify the capability status of a system under certain conditions
Features:
1) The main purpose of this method is to verify whether the system has the capabilities claimed by the system.
The method includes: determining the user scenario, giving the performance indicators that need attention, test execution, and test analysis.
2) The method requires prior knowledge of typical scenarios of the system under test, with defined performance goals
3) This method requires that the environment be determined
4. Configuration test
Definition: Through the adjustment of the software and hardware environment of the system under test, understand the degree of impact of various environments on system performance, so as to find the optimal allocation principle of various system resources
Features:
1) The main purpose of this method is to understand the degree of influence of various factors on the performance of the system, so as to determine the most worthwhile tuning operation
2) This method is generally carried out after a preliminary understanding of the system performance
Need to be carried out under defined environment, operating procedures and pressure conditions
3) This method is generally used for performance tuning and planning capabilities
5. Concurrency testing
Definition: Simulate whether there are deadlocks or other performance problems when multiple users access the same application, module or data record concurrently
Features:
1) The main purpose of this method is to discover possible concurrent access problems in the system
2) This method focuses on possible concurrency issues in the system. For example: memory leaks, thread locks and resource contention issues
3) This method can be used at various stages of development and requires the cooperation and support of relevant testing tools
Commonly used tools: commercial software loadrunner: complete and powerful functions, large memory usage, charges are required
Open source tool jmeter: open source free, free, easy to operate, can assist in the completion of some daily testing work
6. Reliability test
Definition: Apply a certain business pressure to the system, let it run continuously for a period of time, and test whether it can run stably under this condition
Features:
1) The main purpose of this method is to verify whether the system supports long-term stable operation
2) The method requires continuous operation under pressure for a period of time
3) During the test, it is necessary to pay attention to the operation of the system
For example: whether there is any significant change in memory usage or other resource usage and response time
7. Failure recovery test
Designed for systems with redundant backups and load balancing
Definition: To detect whether the system can continue to be used if a partial failure of the system occurs
Features:
1) The main purpose of this method is to verify whether the system can continue to be used under partial failure
2) This method needs to point out: "how many user accesses can be supported" and "what emergency measures to take" when a problem occurs
Generally, this type of test is only required for systems that have clear indicators for the continuous operation of the system
The above types are a summary of the knowledge points in the book. The following lists my understanding of concurrency, load, and pressure. . . . . .
Load test: Make the system reach the bottleneck by continuously increasing the pressure, and provide reference data for tuning
pressure test:
1) Stability stress test: Under different given conditions (such as memory usage, how many requests are made within a certain period of time, etc.), the processing and response capabilities of the system (the fault tolerance and recovery capabilities of the system will be considered here) )
2) Destructive stress test: pressurize continuously until the system crashes and hangs up to find out where the system's maximum bearing capacity is
Concurrency test: A simple understanding is that there are a large number of requests to be processed in a short period of time in business scenarios, which generally appear in login or some important modules and buttons.
8. Mind map
