GB/T 9386-1988 Specification for the preparation of computer software test documentation
Some standard content:
1 Introduction
National Standard of the People's Republic of China
Specification for the preparation of computer software test documents
Specification for the preparation of computer software test documents 1.1 Purpose and Function
GB 9386-88
This specification specifies the preparation of software test documents. Testing is an independent and critical stage in the software life cycle and an important means to ensure software quality. In order to increase the probability of detecting errors and enable testing to be carried out in a planned and orderly manner, test documents must be prepared. Standardized test documents are like a universal reference system that can facilitate communication. The contents specified in the documents can be used as a checklist for the completeness of the test process. Therefore, the use of these documents will improve the visibility of each stage of the test process and greatly improve the manageability of the test work. 1.2 Applicable Objects and Scope
This specification is formulated for software managers, software developers and software maintainers, software quality assurance personnel, auditors, customers and users.
This specification is used to describe a set of test documents that describe the test behavior. This specification defines the purpose, format and content of each basic document. The documents described focus on the dynamic test process, but some documents are still applicable to other types of testing activities. This specification can be applied to software running on digital computers. Its scope of application is not limited by the size, complexity or importance of the software. This specification is applicable to the preparation of test documents for initial development of software and for the preparation of test documents for subsequent updated versions of the software product. This specification does not require the use of specific test methodologies, techniques, equipment or tools. It neither specifies nor mandates specific methodologies for document control, configuration management or quality assurance. Depending on the methodology used, additional documents may need to be added (such as "quality assurance plans"). This specification applies to documents on paper as well as documents on other media. If the electronic document preparation system does not have a secure approval record mechanism, the documents with approval signatures must be on paper. 2 Referenced standards
GB /T 11457 Software Engineering Terminology
GB856 Computer Software Development Specification
GB8567 Guide to the Preparation of Computer Software Product Development DocumentsDefinitions
This chapter defines the key terms used in this specification. s.1 Design leveldesign level
Design decomposition of a software item (such as system, subsystem, program or module). 8.2 Pass criteriapass criteria
The basis for judging whether a software item or software feature has passed the test. .3 Software featuresoftware featureThe significant characteristic of a software item. (such as function, performance or portability, etc.)3.4 Software itemsoftware item
Approved by the Ministry of Electronics Industry of the People's Republic of China on April 26, 1988 and implemented on December 1, 1988
GB9386-68
Source code, object code, job control code, control data or a collection of these items. 3.5 Test item
Software item that is the object of test.
Overview
4.1 Main content
This specification defines the format and content of each test document. The document types proposed include test plan, test description and test report.
The test plan describes the scope, method, resources and progress of the test activities. It specifies the items to be tested, the features to be tested, the test tasks to be completed, the responsibilities of the personnel in charge of each task and the risks associated with this plan. The test description includes three types of documents:
(1) Test design description, which describes the test method in detail, specifies the features included in the design and its related tests, and also specifies the test cases and test procedures required to complete the test, and specifies the passing criteria of the features. (2) Test case description: Lists the specific values used for input and the expected output results, and specifies various restrictions on the test procedures when using specific test cases. Separating test cases from test designs allows them to be used in multiple designs and reused in other situations.
(3) Test procedure description: specifies all the steps required to implement the relevant test design for running the system and executing the specified test cases.
The test report includes four types of files:
(1) Test item transfer report: specifies the test items that are transferred for testing when the development team and the test team work independently or when they want to officially start testing. (2) Test log, which is used by the test team to record what happens during the test execution. (3) Test event report: describes all events that occurred during the test execution and require further investigation. (4) Test summary report: summarizes the test activities related to the test design description. The relationship between these files and other files in terms of compilation and their correspondence with the test process are shown in Figure 1. 4.2 Implementation flexibility
In GB85B7, the files related to software testing are "test plan" and "test analysis report". The eight test documents in this specification are supplements and refinements of the above two documents, which can make the writing of the documents more specific and more referenceable. The test plan can be refined into the test plan, test design description, test case description and test procedure description of this specification, and the test analysis report can be refined into the test item transfer report, test log, test event report and test summary report of this specification. Each unit using this specification should specify the specific files that should be available during the test phase, and specify all the files that can be submitted after the test is completed in the test plan. The types of selected files may also be different for different design layers or different scales of software. In each standard document provided, the content of each chapter can be increased or decreased for specific applications and specific test phases. Not only can the content be adjusted, but additional files can be added to the basic file set. Any file can add new content, and if there is no content to be written in a chapter, it can be omitted, but the number of the chapter must be retained. Each unit using this specification should supplement the requirements and agreements for the content to reflect its specific methods, equipment and counties used in testing, document control, configuration management and quality assurance. Appendix A (reference) will describe the document preparation implementation and use guidelines. 4.3 General requirements Test design Test requirements Test table GB9386-88 Test or plan Test design Test conduct Test performance table Test prohibition Test sensitive station Test compliance Test design Figure 1 Relationship between test documents and test process Test items Test item delivery This specification specifies the text of this specification Documents not specified in this specification |tt||Test items (not specified in this specification]
This specification table specifies the treatment
The following will describe the writing format and content of each test file. For each file, the chapters should be arranged in the specified order. The supplementary chapters can be placed at the end or before the word "approval" (if the last chapter of the file is "approval"). If part or all of the content of a chapter is in another file, the referenced materials should be listed in the corresponding content position. The referenced materials must be attached to the back of the file or handed over to the user of the file. 5 Internal requirements||tt| |5.1 Test plan
The structure of the test plan is shown in Table 1.
1 Test plan name
3 Test items
Tested features
Features not tested
6 Methods
Item passing criteria
8 Suspension standards and restart requirements
3 Test documents to be provided
10 Test tasks
11 Environmental requirements
12 Responsibilities
13 Personnel and training requirements
14 Schedule
15 Risks and contingencies
1 6 Approval
Details of each chapter are given below. 5.1.1 Test plan name (Chapter 1 of this plan) Give this test plan a special name. 5.1.2 Introduction (Chapter 2 of this plan)
GB9388-88
Table of Contents Test Plan
Summarize the software items and software features required to be tested, which may include system objectives, background, scope and reference materials, etc. In the top-level test plan, if the following documents exist, they need to be referenced: project plan, quality assurance plan, relevant policies, relevant standards, etc.
6.1.3 Test Items (Chapter 3 of this plan) describe the object to be tested, including its version, level of maintenance, and indicate the requirements for logical or physical transformations before testing begins. 5.1.4 Features to be Tested (Chapter 4 of this plan) specify all software features to be tested and their combinations, and specify the test design instructions for each feature or feature combination. 5.1.5 Features Not to be Tested (Chapter 5 of this plan) specify all features and meaningful combinations of features not to be tested and their reasons. 5.1.6 Methods (Chapter 6 of this plan)
Describe the overall approach to testing, specify the main activities, techniques, and tools required to test the specified feature group, and describe the methods in detail so that the main test tasks are listed and the time required to perform each task is estimated. Specify the minimum level of testing thoroughness desired, and specify the techniques used to judge test thoroughness (such as: checking that some statements have been executed at least once). Indicate the main constraints on testing, such as: test item availability, availability of test resources, and test deadlines. 5.1.7 Pass criteria (Chapter 7 of this plan) specifies the pass criteria for each test item. GB 9346 --88
5.1. Suspension criteria and restart requirements (Chapter 8 of this plan) specifies the criteria for suspending all or part of the test activities related to the test items in this plan. Specify the test activities that must be repeated when the test is restarted.
5.1.9 Test documents to be provided (Chapter 9 of this plan) specifies the documents to be submitted after the test is completed. These documents can be all or part of the above eight documents. 5.1.10 Test tasks (Chapter 10 of this plan) specify the set of tasks required to perform the test, specify all dependencies between tasks and all special skills required. 5.1.11 Environmental requirements (Chapter 11 of this plan) specify the necessary and desired properties of the test environment. Including: the physical characteristics of hardware, communications and system software, how to use them, and any other software or equipment required to support the test, specify the required special test tools and other test requirements (such as publications or office space, etc.). Identify the sources of all requirements that are not currently available to the test team. 5.1.12 Responsibilities (Chapter 12 of this plan)
Identify the groups responsible for resource management, design, preparation, execution, supervision, review, and arbitration. Also identify the groups responsible for providing the test items identified in 5.1.3 and the environmental requirements identified in 5.1.11. These groups may include developers, testers, operators, user representatives, data managers, and quality assurance personnel. 5.1.13 Personnel and Training Requirements (Chapter 13 of this plan) Identify the level of test personnel required and the training courses available to acquire the necessary skills. 5.1.14 Schedule (Chapter 14 of this plan) Include the test milestones specified in the software project scan schedule and the delivery time of all test items. Define the required new test milestones, estimate the time required to complete each test task, specify the schedule for each test task and test milestone, and specify the use period for each test resource. 5.1.15 Risks and Contingencies (Chapter 15 of this plan) predict the risks in the test plan and specify contingency measures for various risks (e.g., delayed test items may require night shifts to catch up with the specified schedule.
5.1.16 Approval (Chapter 16 of this plan) specifies that this plan must be approved by certain people (name and position). Leave space for signatures and fill in dates. 5.2 Test Design Description
Thank you for the test design description as shown in Table 2.
Table 2 Test Design Description
1 Test Design Description Name
2 Characteristics to be tested
Method details
Hands-on test case name
5 Characteristics passing criteria
The following is a detailed description of each chapter of this specification. 5.2.1 Test design specification name (Chapter 1 of this specification) Give each test design specification a special name. If it exists, you can also refer to the name given in the relevant test plan. 5.2.2 Characteristics to be tested (Chapter 2 of this specification) Define the test items, describe the characteristics that are the test targets of this design and the characteristics of the characteristics. Combination, other characteristics can be mentioned, but do not need to be tested. 5.2.3 Method Detailed Description (Chapter 3 of this specification) The method specified in the test plan is refined, including the specific test technology to be used, and the method of analyzing the test results (such as comparison procedures or manual observation).
GB9386-88
Specify all analysis results that provide a reasonable basis for selecting test cases. For example, the rules for fault tolerance can be described (such as: the conditions for distinguishing valid input from invalid input).
Summarize the common attributes of all test cases, which may include input speed conditions, shared environment requirements, requirements for shared special procedures, and dependencies between any shared test cases. 5.2.4 Test Case Name (Chapter 4 of this specification) List the name and brief description of each test case related to this design. A specific test case may appear in multiple test design specifications. List the procedures related to this test design specification and their brief descriptions. 6.2.5 Feature Pass Criteria (Chapter 5 of this specification) Specify the criteria used to determine whether features and feature combinations have passed the test. 6. 3 Test case description
The structure of the test case description is shown in Table 3.
Table 3 Test case description
1 Test case description name
2 Test items
3 Input description
Output description
5 Environmental requirements
6 Special procedure description
7 Dependencies between test cases
Since test cases may be referenced by multiple test design specifications used by multiple groups for a long time, the test case description must contain sufficient specific information for reuse. The following is the detailed content of each chapter of this specification. 5.3.1 Test case description name (Chapter 1 of this specification) Give this test case description a special name. 5.8.2 Test items (Chapter 2 of this specification) Specify and briefly describe the items and features to be involved in this test case. For each item, consider referencing the following documents: requirement specification, design specification, user manual, and operation manual. 5. Table 8 Input Specification (Chapter 1 of this specification) Specifies the various inputs required to execute the test case. Some inputs can be specified by value (allowing appropriate tolerances). Other inputs, such as constant tables or transaction files, can be specified by name. Specify all appropriate databases, files, terminal information, memory resident areas, and values transferred by the operating system. Specify all required relationships between inputs (such as timing relationships, etc.). 5.8.4 Output Specification (Chapter 4 of this specification) Specifies all outputs and characteristics of the test item (such as response time). Provide the correct value of each output or characteristic (within an appropriate tolerance range).
5.8.5 Environmental Requirements (Chapter 5 of this specification) 5.3.5.1 Hardware
Specify the hardware features and configuration required to execute this test case (such as: 80 characters × 24 lines display terminal). 5.8.5.2 Software
Specify the system software and application software required to execute this test case. System software can include operating systems, compilers, simulators, and test tools.
5.3.6.3 Others
GB9386-88
Describe all other requirements, such as special facility requirements or specially trained personnel. 5.3.6 Special procedure requirements (Chapter 6 of this specification) Describe all special restrictions on the test procedure for executing this test case. These restrictions may include specific preparation, operator intervention, determination of special outputs and cleanup processes. 5.3.7 Dependencies between test cases (Chapter 7 of this specification) List the names of test cases that must be executed before this test case and summarize the dependency properties. 5.4 Test procedure description
The structure of the test procedure description is shown in Table 4.
Table 4 Test procedure description
1 Test procedure description name
2 Date
3 Special requirements
4 Procedure steps
The following is the detailed content of each chapter of this specification. 5.4.1 Test Procedure Description Name (Chapter 1 of this specification) Give each test procedure description a special name and provide a reference to the relevant test design description. 5.4.2 Purpose (Chapter 2 of this specification)
Describe the purpose of this procedure. If this procedure executes test cases, reference the relevant test case descriptions. 5.4.3 Special Requirements (Chapter 3 of this specification) Indicate all special requirements for executing this procedure, including prerequisite procedures, specialized skill requirements, and special environmental requirements. 5.4 Procedure Steps (Chapter 4 of this specification) 5.4.4.1 Log
Describe any special methods or formats used to record the results of test execution, observed events, and other test-related events (see Section 5.6 Test Log and Section 5.7 Test Event Report). 5.4.4.2 Prepare
Describe the sequence of actions necessary to prepare for the execution of the procedure. 5.4.4.3 Start
Describe the actions necessary to start the execution of the procedure. 5.4.4.4 Process
Describe the actions necessary during the execution of the procedure. 5.4.4.5 Measure
Describe how to measure the test (e.g., describe how to use a network simulator to measure the response time of a remote terminal). 5.4.4.6 Pause
Describe the actions necessary to suspend the test due to an unexpected event. 5.4.4.7 Restart
Specify all restart points and the actions necessary to restart the procedure at each restart point. 5.4.4.8 Stop
Describe the actions necessary to stop the execution normally. 5.4.4.9 Cleanup
Describe the actions necessary to restore the environment.
5.4.4.10 Emergency
GB 9356—8B
Describe the actions necessary to handle abnormal events that may occur during execution. 5.6 Test Item Transfer Report
The structure of the test item transfer report is shown in Table 5. Table 5 Test Item Transfer Report
1 Transfer Report Name
2 Transfer Item
3 Quantity
4 Status
5 Approval
Details of each chapter of this report are given below. 5.5.1 Transfer Report Name (Chapter 1 of this report) Give this test item transfer report a special name. 5.5.2 Transfer Item (Chapter 2 of this report) Specify the item being transferred and its version/revision level. Provide relevant information about the item documents and test plans related to the transfer item, and indicate the person responsible for the transfer item.
5,5.3 Location (Chapter 3 of this report)
Specify the location of the transfer item and the media on which it is located. 5.5.4 Status (Chapter 4 of this report)
Describe the status of the transferred test item, including its differences with the item file, previous transfers of these items, and the test plan. List the incident reports that are expected to be resolved by the transferred item. 5.5.5 Approval (Chapter 5 of this report)
Specify who (name and position) must approve this transfer report, and leave space for signatures and dates. 6.6 Test Log
The structure of the test log is shown in Table 6.
Table 6 Test Log Points
1 Test Log Name
2 Summary
3 Activities and Events
Details of each chapter of this report are given below. 5.6.1 Test Log Name (Chapter 1 of this log) Give this test log a unique name. 5.6.2 Description (Section 2 of this log)
Information from all entries in the log, except where otherwise noted in the log entry, is included in this section. The following information should be considered:
(1) Specify the item being tested and its version/revision level. Reference to the test report for each item, if any. (2) Specify the attributes of the environment in which the test was performed, including a description of the equipment, the hardware used, the system software used, and available resources such as available storage capacity.
5.6.3 Activity and event entries (Section 3 of this log) GB Special 3#—Shared 8
For each event (including the start and end of the event), record the date and time of occurrence and indicate who recorded it. The following information should be considered.
5.6.3.1 Execution Description
Record the name of the test procedure executed and reference the test procedure description. Record the people present during the execution, including: testers, operators, and observers, and indicate the role of each person. 5.6.3.2 Test Results
For each execution, record the manually observable results (such as error messages generated, abnormal terminations, and requests for operator actions, etc.), as well as the location of all outputs (such as tape numbers, and whether the test execution was successful). 5.6.8.3 Environmental Information
Record any special environmental conditions for this item. 5.6. 3.4 Unexpected Events
Record unexpected events and the circumstances before and after they occurred (such as requesting to display the total, the screen shows the positive tape, but the response time seems abnormally long, and the response time is also too long when repeated execution). Record the surrounding circumstances that prevented the test procedure from being started or the test from being completed (such as power failure or system software problems).
5.6.8.5 Event Report Name
Record the name of each test event report as it is generated. 5.7 Test Event Report
The test event report structure is shown in Table 7.
Table 7 Test Event Reportbzxz.net
1. Test Event Report Name
2. Summary
3. Event Description
4. Impact
Details of each chapter of this report are given below. 5.7.1 Test Event Report Name (Chapter 1 of this report) Give this test event report a special name. 5.7.2. Summary (Chapter 2 of this report)
Briefly describe the event, indicate the relevant test items and their version/revision levels. Reference the relevant test procedure description, test case description and test log.
5.7.3. Event Description (Chapter 3 of this report) Describe the event. The description should include the following items: Input
Expected results
Actual results
Anomalies
Date and time
Procedure steps
Intention to repeat
Tester
Observer
GB 9$86-88
The description should include relevant activities and observations that help determine the cause of the incident and correct the errors. For example: describe the execution of all test cases that may have affected this incident, describe any differences from the published test procedures, etc. 5.7.4 Impact (Chapter 4 of this report)
Indicate the impact of this incident on the test plan, test design specification, test procedure specification or test case specification to the extent known.
5.B Test Summary Report
Test Summary Report Conclusion The structure is shown in Table 8.
Table 8 Test Summary Report
Test Summary Report Name
Test Adequacy Evaluation
Results Summary
Activity Summary
Details of each chapter of this report are given below. 5.8.1 Test Summary Report Name (Chapter 1 of this report) Give this test summary report a special name. 5.8.2 Brief Description (Chapter 2 of this report)
Summarize the evaluation of the test items, indicate the traced test items and their versions/revision levels, and indicate the environment in which the test activities occurred. For each test item, if there are documents such as test plans, test design specifications, test procedure specifications, test item transfer reports, test logs and test event reports, they can be referenced. 5.8.3 Differences (Chapter 3 of this report)
Report the differences between the test items and their design specifications, and indicate the differences with the tests described or involved in the test plans, test design specifications or test procedure specifications, and explain the reasons for the differences. 5.8.4 Test Adequacy Evaluation (Chapter 4 of this report) Evaluate the adequacy of the test process according to the adequacy criteria specified in the test plan (if any). Indicate the features or feature combinations that are not fully tested and explain the reasons. 5. Table, 5 Results Overview (Chapter 5 of this report) Summarize the results of the test, indicate all resolved incidents, and summarize their solutions. Indicate the incidents that have not been resolved. 5.8.6 Evaluation (Chapter 6 of this report)
Make an overall evaluation of each test item. This evaluation must be based on the test results and the passing criteria of the item. 5.8.7 Activity Summary (Chapter 7 of this report) Summarize the main test activities and events. Summarize resource consumption data, such as: overall level of personnel, total machine time and time spent on each major test activity.
5.8.B Approval (Chapter 8 of this report)
Specifies who (name and position) must approve this report, and leaves space for signatures and dates. A1 Implementation Guide
GB9386-88
Appendix A
Guide to the implementation and use of document compilation
(reference)
In the initial stage of implementing test document compilation, test plan and test report documents can be compiled first. The test plan will provide the basis for the entire test process. The test report will encourage the test unit to record the entire test process in a good way. After a period of practice and accumulation of certain experience, other documents will be gradually introduced. Test document compilation will eventually form a file hierarchy corresponding to the design layer, that is, system test files, subsystem test files, and module test files. The documentation of specific test technologies used in this unit can be used as a supplement to the basic file set described in the text. A2 Usage Guide
In the project plan and unit standards, it should be specified which test files are required in which test activities, and some content can be added to the files to adapt each file to a specific test item and a specific test environment. Table A1 is an example of test files required in various test activities. The number of files required will vary from unit to unit. Table A1
Subsystem
Additional notes,
Test plan
Test design
Test case
An example of test file preparation
Test procedure
This standard was drafted by Shanghai Computer Software Technology Development Center. The main drafters of this standard are Zhu Sanyuan and Chen Min. Test item
Transmission report
Test log
Test event
Test summary
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.