Test documents that testers must master

Software test documents are generally a set of documents that provide test information, which can be tools for testers or development aids for project development teams.

In general, there are mainly the following test documents related to the project.

1. Test plan. (for details, please refer to what elements a standard test plan contains.) after the test plan has been prepared by the test team, it needs to be reviewed with the relevant personnel in the project to ensure that the current plan is consistent with the progress of the project.

two。 Test the strategy. In general, larger projects have additional test strategy documents, that is, detailed test designs. Similar to the summary design document in the development team. After the completion of the test strategy document, it also needs to be reviewed by the relevant project managers and developers. While understanding the test design, you can analyze and compare your own development habits and error points, so that developers can avoid some Bug in the early stage of the project.

3. Test case documentation. It has been mentioned earlier that how to improve the thinking of test case design, it can be seen that test case is an activity to examine the real testing skills and level of testers. At the same time, test cases are generally written according to the test plan and test strategy, and the granularity and test scope of case design will be clearly written in the test plan, and some design methods mentioned in the test strategy will be used. At the same time, combined with the characteristics of the business in the current project to complete and orderly writing. When reviewing with the project team, the purpose is to check and fill in the gaps, so that the project manager has a clear coverage, so as to assess the project risk more accurately.

4. Test report. Mainly for project related personnel such as project managers, product managers, development managers, test team members and management to consult, in order to obtain the test progress of the project, product problems and other information. And provide a reference basis for later iterative projects.

5. Defect report. The main purpose of this paper is to record the relevant quality information of the product, so that the relevant members of the project can understand the defect concentration area and defect type, and show it more intuitively by using the statistical chart.

The personal documentation of test members is also mainly to assist testing, but also summarized in the testing process, in order to enhance their own skill base.

1. Test the requirements architecture diagram. That is, the tester redesigns the test requirements document according to the product document in order to sort out the test document better when writing the test document. And check its testability statically.

two。 User documentation. For third-party testing or professional business systems, user documents need to be written by tests. In other words, the instructions for the use of the system need to be illustrated, so that users in non-professional fields can easily follow the instructions.

3. Draft test. That is, during the testing process, the complex scenarios or functions that need to be calculated are designed, or some test input data need to be recorded.

4. Test notes. Take notes of new skills learned during the test or if in doubt. It is used for reference in the summary.

5. Test the shared library. Templates can be written before the project starts, and each test team member can collaborate during the project. For example, the high frequency of Bug, the more bizarre Bug, the supplement of general function test points, some test ideas of epiphany, and so on, can be written into the shared library, which can be consulted at any time during the testing process, which can save a lot of time. Write it down as testing experience after the project to pay attention to in the follow-up project.