GB/T 38639-2020Systems and software engineering—Software combinatorial testing method (English PDF)
系统与软件工程 软件组合测试方法
This is a limited preview
Buy now to download the full PDF (34 pages)
Need quotation for your management?
Get a formal quotation for GB/T 38639-2020 in 30 minutes.
Issued by
SAMR; SAC
Level / Type
National · Recommended
Issue date
April 28, 2020
Implementation date
November 1, 2020
Scope
GB/T 38639-2020 is the English-translated version of 系统与软件工程 软件组合测试方法.
GB/T 38639-2020 fixes the input preprocessing method and the setting of combination strength for software combinatorial testing, and specifies the constraints and seeds of a combinatorial test, the requirements on the test process and the way the test input and output are represented.
Clause 1 applies the standard to test case design and adequacy assessment for software combinatorial testing, and the page records no exclusions.
Its contents list names clause 3 on input preprocessing, clause 4 on combination strength, clause 5 on constraints and seeds, clause 6 on process requirements and clause 7 on the representation of input and output, with informative appendices on software integrity levels and the matching combination strength and on a worked example, and a normative appendix giving the XML Schema for the test input and output.
Clause 2 defines the combinatorial test method as software testing based on combinations of several parameters, treating the application under test as a black box whose behaviour depends on the interaction of its input parameters, and it also defines combination strength, parameter, value range, variable strength, test case set and seed, a seed being a combination of values the user requires to be tested.
Clause 5 names unconditional constraints, under which any test case must satisfy the constraint expression, requires constraint expressions to support relational and logical operators including equal to, not equal to, greater than, greater than or equal to, less than and less than or equal to, and rules that a seed inconsistent with the model file has its unknown parameters, unknown values and constraint-violating entries ignored.
Clause 6 lays the process out in seven steps: determine the test scope and the functions and parameters to be tested, derive the test conditions and the value range of each parameter, derive the test coverage items as parameter and value pairs matching the combination strength, derive test cases until every coverage item appears in at least one of them, split an oversized set of test cases by a key parameter, hand the set to the tester for execution, and assess adequacy by computing the coverage of the strength combinations against Appendix A. Clause 7 requires the input to carry the combination strength and the definition of every parameter along with any variable strength, seed and constraint definitions, and names XML and JSON as the usual formats, XML where parsing speed and reliability matter and JSON where test data is transmitted remotely and transmission efficiency matters.
The standard carries ICS code 35.080 and Chinese classification L77, was issued on 28 April 2020 and has applied since 1 November 2020.
Found what you need?
Document preview — GB/T 38639-2020
National Standard of the People's Republic of China
- ICS
- 35.080
- Classification
- L 77
Issued by: State Administration for Market Regulation; Standardization Administration of the PRC
Contents
- Foreword
- 1 Scope
- 2 Terms and definitions
- 3 Input preprocessing
- 4 Combination strength
- 5 Constraints and seeds of combined testing
- 6 Combined test process requirements
- 7 Combined test input and output representation
- Appendix A (informative appendix) Software integrity level and combination strength requirements reference
- Appendix B (informative appendix) Example of combined test method
- Appendix C (Normative Appendix) Combined Test Input and Output XMLSchema
- References
1 Scope
This standard provides the input preprocessing method and combination intensity setting of software combination test, and specifies the combination test constraint conditions, seeds, the combined test process requirements and the input and output representation methods of the combined test.
This standard applies to the use case design and adequacy assessment of software combination testing.
2 Terms and definitions
The following terms and definitions apply to this document.
2.1 Combined test method
A method for software testing based on a combination of multiple parameters.
Note: In the combined test, the tested application is abstracted as a black box, which has multiple input parameters, and its behavior is affected by the combined test between the input parameters.
2.2 Combination strength
It is used to indicate the complexity of the test parameter value combination.
2.3 Parameter
Input parameters, configuration parameters or environmental parameters related to the test target.
Note 1. The parameter types include integer, floating point, boolean and string types.
Note 2. The parameters of the software to be tested can be function input parameters, command line parameters, form input boxes, configuration items in configuration files.
2.4 Ranges
The range or set of parameter values.
2.5 Variable intensity
Different combination strength requirements are given for different parameter subsets.
Note: A special requirement of combination strength in combination test. Usually on the basis of the default combination strength, certain parameter subsets of the software to be tested use a combination strength different from the default value.
Example: A system has five parameters a, b, c, d, and e, and the default combination intensity is 2. Among them, the three parameters a, b, and c need to be set to 3 intensity combinations due to special requirements.
Then the test case of the system needs to satisfy the 2-strength combination of the five parameters a, b, c, d, and e, and the 3-strength combination of the three parameters a, b, and c.
2.6 Test case set
A collection of test cases for specific test objectives.
2.7 Seed
In the combination test, the user defines the combination of values that should be tested.
5 Constraints and seeds of combined testing
5.1
Row constraints, otherwise no constraints.
b) Unconditional constraints. Unconditional constraints do not require constraints. Any test case should satisfy the constraint expression.
Constraints and constraint expressions should support relational operators and logical operators.
Relational operators can include, but are not limited to, equal to (==), not equal to (!=), greater than (>), greater than or equal to (>=), less than (<), and less than or equal to (<=), etc.
5.2 Seeds
The combined test method should be able to support the seed of the test case for the specified parameter value.
The parameters, values and constraints of the seed should be consistent with the parameters in the model file. If inconsistent, the seeds should be treated according to the following principles.
a) Ignore that the seed contains parameters that do not exist in the model file;
b) Ignore parameter values in the seed that do not exist in the model file;
c) Ignore that the constraints defined in the model file are violated in the seed.
6 Combined test process requirements
The test process of the combined test is as follows.
a) Determine the test scope. determine the software functions and parameters to be tested.
b) Export test conditions. Determine the value range for each parameter, and determine the value range of continuous variable parameters according to the input preprocessing method in Chapter 4.
c) Derive test coverage items. adopt the method of combined testing and generate test coverage items according to the combination strength defined by the combination. In the combined test, the test coverage item should include the "parameter-value" pair that matches the test item parameter and the combination strength.
d) Export test cases. Generate test cases based on test coverage items until each test coverage item is included in at least one test case.
e) Allocate test case sets. When the number of test cases is too large, the test cases can be divided into different values based on a key parameter, equipped with different test case sets.
f) Test execution. hand over the test case set to the tester for execution.
g) Adequacy assessment. Calculate the coverage rate of the intensity combination, and refer to Appendix A to give a conclusion of full compliance or partial compliance, and the reasons for meeting the requirements.
Appendix B gives a complete example of combined test case generation.
7 Combined test input and output representation
7.1 General requirements
The combination test input should include the combination strength and the definition of each parameter, and should include the variable strength definition, seed definition and constraint conditions of the specified parameters.
Common input and output formats include XML format and JSON format. XML format is suitable for high parsing rate requirements and reliability Test environment with high performance requirements; JSON format is suitable for test environments that require remote transmission of test data and require high transmission efficiency.
See Appendix C for the input and output format files of the combined test.
Appendix B (Informative appendix) Examples of combined test methods
B.1 Overview
This appendix presents the test case generation of a system's test project using the combined test method.
B.2 Parameters
This system has five parameters, namely platform, number of CPU cores, main memory capacity, external memory interface and operating system, all of which are of string type. The value range is as follows.
---The value range of the platform. x86, ia64, amd64.
---The value range of the number of CPU cores. Single, Dual, Quad.
---The range of the main memory capacity. 128MB, 4GB, 64GB.
---The value range of the external memory interface. SCSI, IDE.
---The value range of the operating system. OS1, OS2, OS3, OS4.
B.3 Combined test requirements
B.3.1 Strength requirements
The default is to cover in pairs.
The three parameters of CPU core number, main memory capacity and operating system require a combination of three strengths.
B.3.2 Seeds
The seeds that this system should test are as follows.
a) The platform is amd64, the main memory capacity is 64GB, and the operating system is OS4;
b) The platform is x86, the main memory capacity is 128MB, and the operating system is OS1.
B.3.3 Constraints
The system parameters have compatibility constraints, and the constraints are as follows.
a) When the platform is ia64 or amd64, the operating system is only allowed to be OS3 or OS4;
b) When the platform is x86, the main memory capacity cannot be 64GB.
B.4 Input representation
B.4.1 XML format
According to the above combined test requirements, the combined test input can be expressed in the following XML format.
......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 34 pages — is available in the English PDF.
Similar standards
How to Download GB/T 38639-2020
- 1
Add to cart
Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.
- 2
Checkout
Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).
- 3
Fast delivery
After payment you'll receive an email confirmation. The English PDF is sent to the same address, usually within minutes and at the latest within 1 business day.
- 4
Invoice included
A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.
Related Standards
GB/T 10003-2026 — Biaxially oriented polypropylene (BOPP) film
GB/T 10004-2026 — Plastic/Plastic laminated films and pouches for packaging
GB/T 10007-2026 — Rigid cellular plastics - Determination of shear properties
GB/T 38639-2020
$455.00