foreword
Performance test casesfive parts: expected target user test, user concurrency test, fatigue strength and large data volume test, network performance test, and server performance test.
When writing specific use cases, it should be carried out according to the actual situation, and the principles of low cost, strategy-centered, cutting, perfecting the model, and concretization should be followed.
The main basis of the Web performance test model is that one type of performance test can be transformed into another type of performance test under certain conditions, and the implementation of these types of performance tests has similarities.
Performance testing for expected metrics
The system will propose some performance indicators in the requirements analysis and design phases. Completing the relevant tests of these indicators is one of the primary tasks of performance testing. These indicators are mainly: the system can support 200 concurrent users, and the system response time should not exceed 20 seconds wait.
This pre-committed performance requirement needs to be verified by testing first.
Independent business performance test
Independent business actually refers to the business corresponding to some core business modules. These modules usually have the characteristics of complex functions, frequent use, and core business.
User concurrency test is the key test content of the core business module. The main content of concurrency is to simulate a certain number of users using the same or different functions of a certain core at the same time, and it lasts for a period of time.
Concurrent testing of the same function is divided into two types, one is to perform exactly the same operation at the same time. Another category is to use exactly the same function at the same time.
Combined business performance test
Usually not all users only use one or a few core business modules, and every functional module of an application system may be used, so web performance testing should not only simulate the same operations of multiple users, but also simulate the differences of multiple users operate.
Composite service performance test is the test closest to the actual usage of users, and it is also the core content of performance test. The combined concurrency of each template is usually simulated according to the actual number of users.
Combined performance test is the test that can best reflect the user's usage. It is often combined with server performance test. While simulating user operations through tools, it also collects server counter information through the monitoring function of test tools to comprehensively analyze system bottlenecks.
User concurrency testing is the core content of combined business performance testing. The prominent feature of combined concurrency is that users are divided into different user groups for concurrency according to their use of the system, and the proportion of users in each group should be matched according to the actual situation.
Fatigue strength performance test
Fatigue strength test refers to the test of running the system with a certain load pressure for a long time under the condition of stable operation of the system. Whether the system is stable after running for a period of time.
Large data volume performance test
One is the performance test for some system storage, transmission, statistical query and other services when a large amount of data is used, mainly for some special core services or daily combined services.
The second is the data test under the limit state, which mainly refers to evaluating the response of the system through performance tests when the amount of system data reaches a certain level. The test objects are also some core services or commonly used combined services.
The third type of large data volume test combines the previous two types of tests, and the two types of tests run simultaneously to generate system performance tests with large data volumes.
The large data volume test is usually carried out in the production environment, and it is separated from the fatigue strength test and carried out in the later stage of the entire performance test. The test of large amount of data can be understood as the core business or combined business test under certain conditions.
Network Performance Test
The main purpose is to accurately show how bandwidth, delay, load and port changes affect the user's response time. In the actual software project, it is mainly to test the relationship between the number of users of the application system and the network bandwidth.
The task of network testing is usually done by system integrators.
Server Performance Test
The primary server performance test mainly refers to monitoring some counter information of the server when the business system is working or other types of performance tests are performed, and the comprehensive performance analysis of the server is performed through these counters to provide a basis for tuning or improving system performance.
Advanced server performance testing is generally performed by dedicated system administrators, such as database servers are tested and tuned by dedicated DBAs.
some special tests
It mainly refers to some special WEB performance tests of configuration tests and memory leak tests.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Partners can click the small card below to receive