Software test type/Defect Classification acquisition _ Software test

Software test Type analysis is one of the important means to refine the condition of software test case, by classifying the test type, the software tester can consider the test conditions from different dimensions and find different types of defects to improve the coverage of the test.

Test type is not a standard, its definition needs to consider the different products within the company, combined with the characteristics of project development and software products, as well as testers in the field of industry skills and experience accumulation. Figure 1 is a few aspects of the test type definition that the author proposes to consider:

Figure 1 Main source of test type

Test type definitions require comprehensive consideration of input from various aspects, including requirements for developing document definitions (including some of the standards and specifications involved), ISO/IEC 9126 quality model, test experience, and analysis of defects discovered during the research and development phase, defect analysis of user feedback after product release, etc. The types of tests that are available after continuous sorting and refinement are created. At the same time, the test type is a continuous iterative and updating process, and the test type can be continuously improved during the testing process.

1) Requirements Document analysis

First, the test object-related software work products, including related standards and specifications, are the most important sources to consider in defining test types. In other words, the specific characteristics of the software products, the implementation of the function, customer-oriented and so on is to determine the test type needs to be considered first. For example: Some software products are focused on the user experience, and some software products are security-critical systems, then they need to define the test type is the first consideration.

2) ISO/IEC 9126 quality model

Different product stakeholders, its description and requirements for software PRODUCT quality are not the same, and testers need to take into account the quality of the product requirements of different personnel. Therefore, a tester cannot design an effective test case (the flaw in user feedback is a powerful example) simply by relying on a product's requirements document. The quality characteristics defined in the ISO/IEC 9126 quality model can provide a good idea for testers to choose the quality characteristics, as shown in Figure 2.

Fig. 2 ISO/IEC 9126 quality model

3 Test Experience

Testers ' experience in industry and software products is also one of the important inputs in the definition of test types. Testers with different working experience and industry experience can improve the test type by presenting different viewpoints and ideas in the process of defining and classifying test types.

4 Defect analysis prior to release

Testers can find a large number of defects in the process of testing, by analyzing the defects found in different products and stages, it also helps to classify and perfect the test types.

5) Analysis of defects after release

Exhaustive testing is impossible, so after the release of a software product, it is always possible to discover different types of defects in the user's site, and to analyze and categorize these defects will also help to refine the test type.

This article is reproduced from the 51Testing Software test network, see more: http://www.51testing.com/html/news.html