GB/T 39788-2021 English PDF (GBT39788-2021)

Delivery: 3 seconds. Download true-PDF + Invoice.
Get QUOTATION in 1-minute: Click GB/T 39788-2021
Historical versions: GB/T 39788-2021
Preview True-PDF (Reload/Scroll if blank)

GB/T 39788-2021: System and software engineering -- Performance testing method
GB/T 39788-2021
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 35.080
L 77
System and software engineering -
Performance testing method
ISSUED ON: MARCH 09, 2021
IMPLEMENTED ON: OCTOBER 01, 2021
Issued by: State Administration for Market Regulation;
Standardization Administration of PRC.
Table of Contents
Foreword ... 3 
1 Scope ... 4 
2 Normative references ... 4 
3 Terms and definitions ... 4 
4 Overview of performance testing ... 6 
5 Performance test process ... 6 
6 Performance test demand model ... 10 
7 Types of performance tests ... 14 
Appendix A (Informative) Quality measure of performance efficiency ... 29 
Appendix B (Informative) Mobile application performance test case ... 30 
Appendix C (Informative) Application case of performance test of large-scale
information system ... 37 
Appendix D (Informative) Test case of cloud application performance ... 41 
Appendix E (Informative) Test case of embedded software performance ... 48 
System and software engineering -
Performance testing method
1 Scope
This standard specifies the test process, test requirement model, test types for
the performance of system and software.
This standard applies to the analysis, design, execution of performance testing
for system and software.
2 Normative references
The following documents are essential to the application of this document. For
the dated documents, only the versions with the dates indicated are applicable
to this document; for the undated documents, only the latest version (including
all the amendments) are applicable to this standard.
GB/T 25000.10-2016 Systems and software engineering - Systems and
software quality requirements and evaluation (SQuaRE) - Part 10: System
and software quality models
GB/T 25000.23-2019 Systems and software engineering - Systems and
software quality requirements and evaluation (SQuaRE) - Part 23:
Measurement of system and software product quality
GB/T 38634.1-2020 Systems and software engineering - Software testing -
Part 1: Concepts and definitions
3 Terms and definitions
The terms and definitions as defined in GB/T 38634.1-2020, AND the following
terms and definitions apply to this document.
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.
Note: A type of performance efficiency test.
4 Overview of performance testing
Performance testing is used to evaluate the extent, to which the system and
software under test complete its designated functions, within a given time and
other resource constraints. It is also called performance efficiency testing.
For the performance efficiency, quality characteristics, sub-characteristics of
system and software, see 4.3.2.2 in GB/T 25000.10-2016. For the performance
efficiency, quality measures of system and software, see Appendix A. The
description and measurement functions of the quality measures are as shown
in 8.3 of GB/T 25000.23-2019. When in use, the quality measures shall be
tailored, according to the actual needs of the system and software.
Refer to Appendix B for cases of test of mobile application performance.
Refer to Appendix C for cases of test of large-scale information system
performance.
Refer to Appendix D for cases of test of cloud application performance.
Refer to Appendix E for cases of test of embedded software performance.
5 Performance test process
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:
a) Determine the admission criteria of the performance test. Execute it after
the system architecture is determined or the smoke test is passed. The
sooner the test is involved, the better.
b) Determine the performance requirements of the system and software to
be tested. Performance requirements can come from requirements, which
are specified in documents such as contracts and requirements
specifications, OR the implicit requirements agreed upon by business,
data, expected users, system behavior. The performance requirements
should be determined, according to the performance requirement model.
- The system is unavailable;
- The server is down OR the necessary services are stopped, due to
uncertain reasons;
- The application has a blocking program/serious defect in the ON
state;
- The required dependencies are not available.
2) Recovery criteria may include:
- The system and/or server are available, turned on and running;
- Resolve blocking and/or critical issues;
- The function of the application has been restored;
- Test the degree of recovery when the data processing cycle is not
completed.
5.4 Execution of performance test
The execution process of performance test includes the following activities:
a) Perform a pre-readiness check, before execution, to evaluate the
environment and resources required for performance testing.
b) Execute test scripts manually or using test tools; monitor performance
indicators during execution; record test results.
c) Performance testing usually needs to examine the comprehensive
performance of the system and software under test, over a period of time;
it takes the average, maximum, or minimum value as the test result, as
needed.
d) If the performance test terminates abnormally OR does not meet the
requirements or expectations, fill in the performance problem report form.
The problem report shall include the source of the problem, scenario
configuration, problem description, problem level, etc.
e) Determine whether the executed test case passes. If the test fails, analyze
the specific situation, to determine whether it is caused by the
performance bottleneck of the software itself OR caused by the test
environment.
Figure 1 shows the execution framework of performance test, which consists of
five components: input, operating environment and system and software under
a) Organize the performance test results. For the results of the performance
test, it should consider the comprehensive results under a variety of
environmental factors; use mathematical and statistical methods for
comprehensive data analysis, such as standard deviations, statistical
models agreed by users.
Note 1: When analyzing data, it should delete abnormal data, such as data
captured when the system is started or shut down.
Note 2: For the considerations of response time, throughput rate, resource
utilization rate, it includes average, minimum, maximum, or standard
deviation.
Note 3: For the number of concurrent requests, it should analyze the
largest concurrent requests.
b) Compile a software performance test report, which should include: test
result analysis, evaluation and suggestions on software performance.
c) Compile performance problem reports, based on test records and
performance problem report sheets. The performance test event report
shall include the source of the problem, scenario configuration, problem
description, problem level, etc.
6 Performance test demand model
6.1 Overview
The performance test demand model shall consider the following facto...