The application of peer review in software testing

This week in the software testing class to learn the peer review method, the following specific introduction of peer review method in the software testing process application.

Peer review activities should focus on defects in the product, not the author or producer of the work product, and the manager should not use the results of peer review to evaluate individual behavior. Peer review is divided into 3 categories.

(1) Formal assessment (inspection), usually by peer-reviewed training project manager or Ppqa presided over, the size of the 3~7 between the appropriate, generally completed a work product after the review. The purpose of the formal review is to locate and remove defects in the work product.

(2) Technical review (Technical reviews), or internal review, usually convened by the technical lead or project manager and attended by more than three people. The technical review is generally conducted in the medium term of the work product or when a part of an independent work product has been completed, and it can also be discussed and reviewed in the case of problems with the drafting of one or two of these issues. It is also possible to check the compliance of work products and procedures, templates, plans, standards, or whether changes have been performed correctly. The purpose of the technical review is to provide improved advice through technical reviews of the developer's work products.

(3) Walk-through (walkthrough), also known as code walking or code for the daytime, the scope of the review according to the requirements of the priority is usually determined by the management, mainly static quality analysis and programming rules check. It is usually a small seminar, generally in the early stages of the formation of a work product, and when the author has some ideas, he hopes to get some help or add some ideas. Of course, it can be done at any stage of the preparation of the work product, with two or three participants and chaired by the author.

Formal review, technical review and three forms of peer review of the importance of different degrees, the purpose, timing, size, preparation time, moderator, participation in the jury, the results are not the same, should strictly follow its procedures, procedures and considerations for peer review to ensure the effectiveness of peer review.

Peer review through the need to meet the following guidelines.
1. Minimum criteria
(1) Work products have been reworked and confirmed;
(2) The moderator has issued a review report.
2. Based on an organization's metrics or an earlier review, you can set export guidelines for such work products
(1) Whether the estimate of the number of remaining major defects is within the limits;
(2) Whether the estimate of the number of remaining minor defects is within the limits;
(3) The number of changes within the scope of the limitation
3. Peer review of the "123 Guidelines": Peer review preparation time is equal to (or greater than) the meeting time, the number of defects found during peer review is more than twice times the number of defects found during peer review preparation, peer review found that the efficiency of defects is 3 times times the test found defects.

Peer review and testing are considered by the industry to be the most effective means of finding defects (the defects found can account for the total number of defects found 80%~90%, so the measurement of both will be more important. Specific measurement procedures, methods, and measures are described in detail in the relevant sections of software metrics in this book. This section describes only the data that should be collected during peer review. In order to effectively improve the quality of the peer review process, it is often necessary to measure the process data, through the measurement analysis can see how the peer review efficiency, test results, as the basis for further improvement of the process, continuous improvement process, improve product quality.

Review is a peer-reviewed one, in the software project occupies an important position. Review (inspection) is a formal peer review that is suitable for software products that are of greater importance and repeatability. The role of the review includes the moderator, the commentator, the recorder, the author and the Examiner. Generally speaking, there are 3 to 7 people involved in the review. The division of roles is as follows:
1. Moderator: The need for leadership skills to manage the review process is a key role in the review process.
2. Provide review materials and provide an overview; In addition, the author can act as a reviewer.
3. Recorder: According to the instructions of the host to record products and procedures and other anomalies, in the recording of the same time to classify the anomalies.
4. Narrator: Fully understand the review materials and explain them at the same time. The role cannot be assumed by the author.
5. Examiners: All persons involved in the review can be examiners, who are primarily responsible for understanding the material being examined, conducting personal examinations, preparing for and participating in review meetings.

　　

The application of peer review in software testing