[Turn] common performance test methods

1. Load test
Here, the loadTestRefers to the most common requirements for verifying general performance.Performance Testing, in the above we mentioned the user's most common performance needs is "Marca, but also horses eat less grass." Therefore, the load test mainly investigates the performance of the software system under the given load. We can understand the load test as follows:
(1) Load test is to stand in the user's perspective to observe the performance of the software system under certain conditions.
(2) The expected result of the load test is that the user's performance needs are met. This indicator is generally reflected in response time, transaction capacity, concurrency capacity, resource utilization, etc.
2. Pressure test
The stress test is to investigate the performance of the system under extreme conditions, which can be overloaded volumes and concurrent users. Note that this extreme condition is not necessarily a user's performance requirement, and may be much higher than the user's performance requirements. As can be understood, stress testing and load testing are different, the expected result of stress testing is the system problems, and we have to examine the way the system handles the problem. For example, we expect a system to be stable in the face of stress, with slower processing speeds but no system crashes. Therefore, stress testing is a way for us to identify the weaknesses of the system and how the program will operate under extreme load.
Example: Load testing is concerned with user rules and requirements, and stress testing is concerned with the software system itself. For their differences, we can use the example of Huashan on the sword to describe it more visually. If Guo Jing as the subject of the test, then the stress test is like Guo Jing and has been the yin, Ouyang Fung pretty upset, no routines, as far as possible to defeat each other. Guo Jing to be able to cope and not to be thrown into a small life. And routine performance test is like Guo Jing and yellow pharmacist, Hong Seven public three agreed, as long as Guo Jingneng respectively two master 100 strokes, Guo Jing even win. As for the 300 strokes, even if the Guo Jing will lose that also do not care. If he can do the next 100 strokes, even through.
Think----"When we do software stress testing, we tend to increase the number of concurrent users and transactions that are more than the load test, which is why?"
3. Concurrency test
Verifies the concurrency of the system. In general, and the server side to establish a large number of concurrent connections, through the response time of the client and server-side performance monitoring to determine whether the system has reached the established concurrency Capability index. Load tests often use concurrency to create the load, and the reason for concurrent testing is that concurrency testing often involves the concurrency of the server, as well as the possible problems of multi-process/multi-threaded coordinated synchronization. This is to be paid special attention and must be tested.
4. Benchmark Test
When a new module is added to a software system, benchmarks need to be tested to determine the performance impact of the new module on the entire software system. In accordance with the benchmark method, the new module needs to be opened/closed at least once for each test. Each performance indicator of the system before closing the module is noted as a benchmark (Benchmark), and then compared with the system performance indicators in the Open module state to determine the impact of the module on system performance.
5. Stability Testing
"Road distance horse horsepower", here we want to talk about the performance testing of the stability test, that is, the test system under a certain load for a long time after the problem will occur. Some problems of software system can not be exposed at once, or it takes time to accumulate in order to achieve the degree of measurement. Why would you need such a test? Because some software problems can only be exposed for a day or one weeks or longer. This problem is usually caused by the application of resources but not released in time. For example, the memory leak problem is that after a period of time accumulation will gradually become significant, in the beginning of the operation is difficult to detect, as well as the client and server after the load has been running for a period of time, the establishment of a large number of connection pathways, but not effectively reused or released in a timely manner.
6. Recoverable test
The test system can quickly recover from the error state to a normal state. For example, in a system with load balancing, the host is under pressure and not normal.work, the backup machine is able to take over the load quickly. Recoverable tests are usually done together with stress tests.
Tip: Each test has a space and purpose for its existence. When we take over a software project, under limited resource conditions, choose which test to do, which should be based on the current software process stage and the project's own characteristics to make choices. For example, in the integration test to do benchmark, in the SOFTWARE product every publishing point to do performance testing.

[Turn] common performance test methods