The test document is an important output in the whole test; the test document also runs through the beginning and end of the test activity; various documents will be produced in the process of test planning, test design, test execution, test acceptance and so on. The ultimate purpose of test documentation is to test more efficiently and to preserve test organization assets. During the testing process, we often encounter various test problems, many of which are document problems. This paper focuses on discussing and solving the following three problems;
1. How to manage test documents?
2. Which documents need to be managed?
3. How to develop documentation habits?
First, let's talk about the first question. The characteristics of test documents are large number, complex content, and need to be shared. To manage them well, I recommend using SVN management tools. At the same time, the document structure needs to be designed and classified to ensure the effectiveness of document management. The document structure is designed as follows: first-level attempts (test management, software testing, hardware testing, public sharing, departmental collaboration); test management refers to documents related to test management work, including test specifications, test procedures, work assessment, management systems, personnel Recruitment, team building, etc.; software testing refers to the project documents related to software testing, including project 1, project 2, project N, etc., of which project 1 includes test plan, test design, test report, automated test, test configuration, etc., other The project reference is as above; hardware test refers to the project and platform documents related to hardware test, including hardware test plan, hardware test record, hardware public library, hardware quality system, hardware board tracking, etc. If hardware test is not involved, please ignore this part ;Public sharing refers to some resources shared by everyone, including testing technology, commonly used software, personal temporary transfer, public library files, laboratory management, general basic knowledge, project technical documents, newcomer training, etc.; Partial collaboration refers to cooperation with R&D, The working documents for the docking of operation and maintenance, products, etc., including development documents, operation and maintenance documents, product documents, etc., mainly record the documents produced by the cooperation of various departments. In addition to the first-level attempts, the second-level attempts, the third-level attempts and the fourth-level attempts, etc., the structural design of the document needs to be flexibly designed according to the needs of the work.
Second, let's talk about which documents need to be managed. We focus on test management, software testing (which may include hardware testing), and public sharing. Test management is mainly about customizing the system, following the process, team performance management and personnel recruitment. The testing system mainly refers to the testing department system (management system, test development, product testing, delivery testing, etc.), job responsibilities, and promotion paths. The test process mainly refers to the test process and test specification of the test department. The test process includes automated test process, product test process, test strategy formulation process, version test process, and delivery test process; test requirement description, test report submission, test case writing, testing Defect submission, test configuration, test process record, measurement analysis report, test work summary, etc.; performance management includes work summary (weekly, monthly, annual), performance appraisal (monthly, annual), attendance scoring, etc. The software testing part mainly consists of four parts: project information, test plan, test execution, and test evaluation. Project information is the basis and main source of information for the testing work to be carried out. The test plan provides general guidelines and general guidelines for conducting tests. Test execution is the landing and implementation of the test plan, in which the test process record sheet, test configuration, and test cases are very important; the test schedule is one of the main sources of information for the full record of the test process and the feedback and adjustment of the test plan; the test configuration is The basis for our efficient execution of tests; test cases are the basis for our execution of tests. Test evaluation is the end of the whole test and is the key to the final quality evaluation of the test product or project, mainly including test results, test analysis reports, and test summary reports; the test results refer to the original test data or the sorted test. Data and test results; the test analysis report focuses on the analysis of test results and defects, draws test conclusions, and evaluates quality; the test summary report includes test plan analysis report, test execution analysis report, test defect analysis report, test resource input report, test report Metric analysis reports, etc.
Finally, let's talk about how to get into the habit of documentation. The formation of any habit takes time and needs to be carried out subtly. Several common document problems are basically that the test document exists on the personal computer, the test document is unwilling to write, the test resource is not shared, the test data is not recorded completely, the test document is not updated in time, and so on. There are two ways to deal with all the above problems: first, use document management tools, formulate corresponding document management systems, and restrict and supervise everyone's work habits, which will naturally change over time; The testing effort is tightly coupled, as an integral part of the testing effort, addressing these issues at their source and at the root. From my work experience, it usually takes about 2 years to manage test documents in an orderly manner, so test managers must be patient, especially for teams who are used to the free working mode at the beginning, and the development of habits is more Patience is required.
The following figure is based on our actual work, lists the basic classification of document management, some of the key content has been expanded, everyone will look more clearly.
