One of the best practices for Software Quality Assurance: Code Review and Case Review

The previous article translated bug analysis, which laid the foundation for Bug prevention and emphasized the prevention of Software defects. Software Quality is built and determined by the quality of the entire process of software development. The software quality is certainly not tested through testing. Therefore, it is important to prevent Software defects from beginning to end. In addition to defect analysis, another important practice is code review and test case review ).

1.Code Review

There is a good practice in many companies such as IBM and Microsoft, that is, code review-code review. This process of code review is not to send the code to one or several people,Instead, it emphasizes that programmers go to the stage on a regular basis to explain their source program activities to others.. Because I want to explain my program to everyone, Show Code to other guys, programmers will pay great attention to their work progress and code quality. When writing code, always think -- may be selected at any time for code review, so take every line of code very seriously. This code review method has other advantages:

• You can learn program design ideas, methods, and skills from each other to improve your skills;

• You can promptly discover code problems, including code dependency issues;

• More people understand the code written by others, and it will become easier to maintain the code in the future.

Therefore, this code review method has been proved to be an effective method.

2.Test Case Review

For code review, perform case review on the test/QA side.EveryQAAll engineers have the opportunity to be selected.PresentationTo make it clear to everyone/How does she design test cases (Test Case)OfIncluding understanding of new features of the product, analysis of the test scope, which factors are taken into account, user scenario, and how to design the use case? What is the test coverage rate? Show the main test cases from start to end, and so on.

Everyone has and must have a chance. This is the key. Second,Case ReviewSelectedQA EngineerHe must be explained/How does she writeTest case.

Through such practices and activities, you can discover problems in test case earlier, inspire each other, learn the skills and methods of test case design, and exchange experiences. We also urge everyone to design test cases.There are also many benefits:

• Before designing the test case, we will consider a variety of factors and think clearly about the design concept-improving the coverage rate.

• Carefully write each test case-Improving the quality of a single case

• Early detection of test case problems, including areas of mutual influence.

• Mutual Learning

• Easier to maintain test case

Code review and test case review also contain"Defect Prevention. To improve the quality, we have to do the right thing for the first time, as krausabi said! If system analysts, architects, designers, programmers, and so on are all about to do the right thing for the first time, testers may not need it. There is an example of a software company in India with thousands of people, there are only 5-6 real QA personnel, but there is no tester, the quality of the software products is still very good, once again verified"Quality is written, not tested".