What is software testing peer review?

　　“ Peer review is a kind of peer review that passes the author ( Development 、 test 、QA etc. ) To confirm the inspection method of defects and areas that need to be changed .” In software testing , Peer review is used to verify software development , Whether the work of each stage of software evaluation is complete , standard , Whether the products in each stage meet the specified technical and quality requirements , To decide whether it can be transferred to the next stage of work . Software review is a necessary work to ensure the smooth progress of software development projects , Often peer review is conducted by 5 Groups of more than people to complete , In a certain period of time , Find as many mistakes as possible , It is an evaluation index to judge whether a peer review meets the requirements .

　　 In peer review , The Department review stage is generally divided into nine stages ：

　　　　1. System analysis and design

　　　　2. Software requirements analysis

　　　　3. System outline design

　　　　4. Detailed software design

　　　　5. Code and unit tests

　　　　6. Software component testing

　　　　7. Software configuration test

　　　　8. Software system test

　　　　9. System reception

　　 Every stage is constantly improving the process of software development , It provides strong support for the whole development stage .

　　 As mentioned above, the stage of peer review is divided into nine different stages , Each stage has its own role , The combination of the nine stages makes software development and testing rational and orderly , Then in the process of Review , How does the general process of peer review proceed ？ The following figure will illustrate the stage process of its operation ：

　                                                             　

　　 The above figure illustrates the implementation of peer review , It is divided into four stages , They are the planning stage , implementation phase , Measurement phase , review / Audit stage . Each stage has specific implementation steps , Among them, during the implementation stage, I will read , Technical review , Formal review , It is the review stage that supports the whole process .

　　 As mentioned above, at least 5 people , So how do these five people allocate roles , The five roles are Moderator、Inspectors、Author、Reader、Recorder These five roles , among Inspectors It can be played by many people .                      

　　 The picture above is in the whole PR In the process , The five roles have their roles and appearance time respectively , Let's talk about the detailed functions of the next five roles ：

　　　　1.Moderator stay PR In the process, I acted as the host , Responsible for ensuring PR The smooth implementation of , And ensure that it is efficient ;

　　　　2.Inspectors stay PR In the process, I acted as a reviewer , It mainly finds some defects and loopholes in software design BUG;

　　　　3.Author It is the designer who reviews the software ;

　　　　4.Reader stay PR As the role of interpreting the software design for everyone ;

　　　　5.Recorder stay PR As a record , This evaluation PR The efficiency of work ;

　　 stay Recorder Record and evaluate this PR The efficiency of work , The specific efficiency will be calculated according to some indicators , There are often the following indicators ：

　　　　1、Defect density = defects/review scale

　　　　2、Review speed = review scale/review hours

　　　　3、Review efficiency = defects/man-hour

　　 The level of these three indicators can almost explain this PR How about efficiency .