GB/T 39788-2021System and software engineering—Performance testing method (English PDF)

3.1 Load testing

It is used to evaluate the performance of the system and software, under the expected varying load. The load is usually between the low, typical and peak usage expectations.

3.2 Stress testing

It is used to evaluate the performance of the system and software, under the conditions of higher than expected or specified capacity load demand, OR lower than the minimum required resources.

3.3 Spike testing

It is used to evaluate the performance of the system and software, in a short period of time, when the load greatly exceeds the normal load.

3.4 Scalability testing

It is used to evaluate the performance of the system and software to adapt to changes in external performance requirements (such as user load support, number of transactions, data volume, etc.).

5.1 Overview

The performance test process includes four processes. demand analysis of performance test, design and implementation of performance test, execution of performance test, summary of performance test.

5.2 Demand analysis of performance test

The demand analysis of performance test includes the following activities.

5.3 Design and implementation of performance test

The design and implementation process of performance test is used to derive test cases and test procedures. Related activities include.

5.4 Execution of performance test

The execution process of performance test includes the following activities.

5.5 Summary of performance test

The summary of performance test includes the following activities.

6.1 Overview

The performance test demand model shall consider the following factors. environment, data, business processes, user distribution, request timing distribution, network status, etc.

6.3 Data requirements

The data required for performance testing includes the following requirements.

6.4 Business process

Performance test shall first consider testing the main or important business processes. Different business processes have different stress on the system.

The following factors shall be considered, based on risk assessment, when selecting business processes.

6.5 User distribution model

The user role distribution of the performance test shall obey the real environment distribution, which can be described by the user distribution model. Example: Figure 2 describes a user distribution model.

6.6 Request timing distribution model

The timing of sending performance test requests shall meet business

6.7 Network status requirements

The requirements for the network status shall be considered from the following aspects.

7.1 Load test

7.1.1 Building a model

The load test model is described by load volume, load business, running time.

Under the condition of specified business load and running time, it measures the load of the tested service.

7.1.3 Export test case

The load test case is exported, according to the following steps.

7.2 Stress test

7.2.1 Build a model

Stress test is used to evaluate whether the software is robust and usable, under extremely heavy loads. It means measuring the state of the system and software, under extreme load, by increasing the system load.

7.2.2 Export test coverage items

For stress testing, the stress test requirement of each tested business is a test coverage item.

7.2.3 Export test case

The stress test case is exported according to the following steps.

7.3 Peak test

7.3.1 Build a model

The peak test model is described by peak load business, peak load intensity, peak duration, monitoring indicators. For the specified load service, when the momentary peak value of the load business (exceeding the strength that the system can normally bears) comes, the system will undergo degraded operation;

7.4.2 Export test coverage items

For scalability test, the scalability test requirement of each tested business is a test coverage item.

7.4.3 Export test case

The scalability test case is exported according to the following steps.

7.6.2 Export test coverage items

For volume test, the throughput indicator and storage capacity indicator of the system and software to be tested are a test coverage item. According to different business requirements and system architectures, the following principles are generally followed when selecting volume indicators.

7.6.3 Export test case

The volume test case is exported according to the following steps.