GB/T 9386-2008 English PDFUS$929.00 · In stock
Delivery: <= 7 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 9386-2008: Specification for computer software test documentation Status: Valid GB/T 9386: Historical versions
Basic dataStandard ID: GB/T 9386-2008 (GB/T9386-2008)Description (Translated English): Specification for computer software test documentation Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L77 Classification of International Standard: 35.080 Word Count Estimation: 42,434 Date of Issue: 2008-04-11 Date of Implementation: 2008-09-01 Older Standard (superseded by this standard): GB/T 9386-1988 Regulation (derived from): Announcement of Newly Approved National Standards No. 6, 2008 (No. 119 overall) Issuing agency(ies): General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China Summary: This standard provides a basic set of computer software test documentation format and content requirements. This standard applies to the whole process of computer software life cycle. GB/T 9386-2008: Specification for computer software test documentation---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.Specification for computer software test documentation ICS 35.080 L77 National Standards of People's Republic of China Replacing GB/T 9386-1988 Computer software test documentation specifications Posted 2008-04-11 2008-09-01 implementation Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China Standardization Administration of China released Table of ContentsPreface Ⅰ Introduction Ⅱ 1 Scope 1 2 Normative references 1 3 Terms and definitions 4 Test Plan 2 5 Test description 5 6 test instructions 5 7 test procedure described 6 Test item 8 8 Delivery Report 9 8 test log 10 Test Incident Report 9 11 test summary report 10 Appendix A (informative) Implementation and Use Guide 12 Annex B (informative) Example 13 test document Annex C (informative) Example 35 delivery reportForewordThis standard is GB/T 9386 "computer software test documentation specifications," the first amendment. This standard and GB/T 9386- 1988 The main difference is as follows. a) according to GB/T 1.1 the provisions of the older part of the Chapter 1 Introduction and Chapter 4 of the original content is transferred to the adjustment The introduction of the new standard; b) the scope of the new standard to rewrite a chapter; c) Chapter 3 Terminology section 10 adds the following terms and definitions. Test test Test Case Description testcasespecification Test description testdesignspecification Test incident report testincidentreport Test (activity) testing Test item delivery report testitemtransmittalreport Test log testlog Test Plan testplan Test procedures described testprocedurespecification Test summary report testsummaryreport d) version of the standard of Chapter 5 of 5.1 to 5.8 were upgraded to the new standard in Chapter 4 to Chapter 11. It was part expansion; e) an increase of Appendices B and C. The Standard Appendix A, Appendix B and Appendix C are informative appendices. From the date of implementation of this standard in place and repealing GB/T 9386-1988. The standard proposed by the People's Republic of China Ministry of Information Industry. This standard by the National Information Technology Standardization Technical Committee. This standard was drafted. Shanghai Pudong Software Platform Co., Ministry of Information Industry Electronic Standardization Institute, Beijing track and pass Letter Institute of Technology, computer software development center in Shanghai, Guangxi Software Park, Shanghai Pudong Software Park Co., Ltd., Shanghai Baoxin Software shares Limited copies. The main drafters of this standard. Feng Hui, Ren Lin, Vang Pao Ai, Zhang Louying, poly Xu Chang, Yang Genxing, Cong Liqun, Zhang , Qi Jianhua. This standard was first published in 1988.IntroductionTest the software life cycle in an independent critical stage, but also an important means to ensure software quality. In order to improve the detection error Chance of error, so that the test carried out in a planned and orderly manner, shall prepare the documentation of software testing. Standardized test document is like a universal The reference system can be achieved to facilitate the exchange purposes. Contents of the document can be used as specified in the relevant test process control completeness check Look-up table, so the use of these documents will improve each stage of the testing process visibility greatly improve testing manageability. This standard specifies the format and content of each test document. Mainly related to the test plan, test instructions and test reports. Test plan describes the scope of testing activities, methods, resources and progress. It provides item being tested, tested features should be completed measurement Test mission, in charge of the work of each person as well as the risks associated with the program and so on. Test description includes three types of documentation. a) Test Design Description. Detailed description of test methods, and to identify the associated test design and test coverage feature, also identified as End To test features and provisions of the guidelines required by the test cases and test procedures; b) Test Case Description. The actual value will be used for input and output is expected to be documented. And identifies the use of specific test cases Time constraints on testing procedures. Design test cases and test separately, so that they can be used for multiple designs, and can be in other cases Shaped lower re-use; c) Test procedure description. Logo for the implementation of the relevant test design and operation of the system and perform all the steps required by the provisions of the test cases. Test procedures and test design separate steps to be followed explicitly and deliberately, and should not contain extraneous details. Test report includes four types of documents. a) Test item delivery report. the circumstances specified in the case of the development and test groups work independently or in hope started to test A test item for the test to be delivered; b) Test log. a test group for recording happens during the execution of the test; c) Test incident report. describe any event occurs during test execution and require further investigation; d) test summary report. summary for testing activities and documentation of results. These documents and other documents prepared in terms of the relationship and the corresponding relations with the test process shown in Figure 1. These documents Guide See Appendix A, compiled examples of these documents refer to Appendix B and Appendix C. This standard is to ensure that staff, auditors, customers and users of software management, software development, testing and maintenance, software quality customized. This standard is used to describe a set of basic software testing and test documents related to the implementation. This standard defines a basic document for each project The format and content. Although the document described in this standard focuses on dynamic testing activities, but some documents still applies to other types of measurement Test activities (for example, the test program can be used to design and code reviews). This standard can be applied to run on a digital computer software business, scientific computing, software, or a military software. Its range of applications from Software size, complexity or criticality limit. This standard applies to both the initial development of software testing documentation, and thereafter apply the soft Products updated version of the test documentation. This standard does not require the use of specific methodologies, techniques and equipment or tools. Document control, configuration management or quality assurance refers neither Forced out specific methods not learn. According to the methodology used, you may need to add some other documents (such as quality assurance programs). This standard applies to both documents on paper, but also to document other media. If the electronic documentation system that does not have security Approved registration mechanism, the document must approve the use of paper signatures. Relationship test documentation and test procedures 1 Computer software test documentation specifications1 ScopeThis standard specifies a set of basic format and content requirements for computer software test documentation. This standard applies to computer software survival The whole process cycle.2 Normative referencesThe following documents contain provisions which, through reference in this standard and become the standard terms. For dated references, subsequent Amendments (not including errata content) or revisions do not apply to this standard, however, encourage the parties to the agreement are based on research Whether the latest versions of these documents. For undated reference documents, the latest versions apply to this standard. GB/T 8566 Information technology - Software life cycle processes (GB/T 8566-2007, ISO /IEC 12207.1995, MOD) GB/T 8567 computer software documentation GB/T 11457 IT software engineering terminology3 Terms and DefinitionsGB/T 11457 and established in the following terms and definitions apply to this standard. 3.1 Decomposition items of software design (e.g., system, subsystem, or module). 3.2 Analyzing item of software or a software feature discrimination on the basis of whether the test passed. 3.3 Notable features of the software items (such as functional, performance or portability). 3.4 Source code, object code, job control code, control data, or a collection of these items. 3.5 a) a set of one or more test cases consisting of; or, b) a set of one or more of the test procedures thereof; or c) one or more test cases and procedures set composed. 3.6 For a test case, to specify the input document, expected results and the implementation of a set of conditions. 3.7 Test method is used to specify a software feature or combination of features of the software details and identifies the associated test documentation. ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 9386-2008_English be delivered?Answer: Upon your order, we will start to translate GB/T 9386-2008_English as soon as possible, and keep you informed of the progress. The lead time is typically 4 ~ 7 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 9386-2008_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 9386-2008_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.Question 5: Should I purchase the latest version GB/T 9386-2008?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 9386-2008 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically. |
