█ Microelectronics same number █ 136 ★ 7010 ★ 9993 ████ ███ Hefei tubes donor eggs IVF surrogacy selected ███ ████ tube package gender boy born boy ████ ████ Surrogacy Surrogacy package born ███ ██ sex surrogate choose IVF surrogacy boy █████ ███
Today, we chat software quality control in which a very important link: Code Review.
Code Review Role
1. improve software quality . Quality control software, the code Review is actually very important aspect, it can find a lot of problems and is very effective. When identify with this one-step method code Review and modify a mistake to spend three work, but will have to spend 12 works by this test method to complete two: Microsoft has done similar statistics, results show . In a program created by the 400 program ape 700,000 lines of code, the code Review the cost-benefit test several times higher than that. Thus, the code Review has great effect on the quality control .
2. improve the ability of the code developers . Code Review can be found by writing all kinds of problems in your code developers, such as: variable naming, code structure design, algorithms, explanatory notes and other issues, by the issue of the exchange, the code will also enhance the ability of developers.
Review of the role of the code
Development Leader or an experienced developer for others to Review (and more generally the case)
Review each other between developers
Testers conduct random checks on the development of the code. Xiao Bian was in the process of testing the project will Review the code, developers often find replicate the problem is not to modify the variable name when pasted, time-tested.
Code Review form
Review Code in order to ensure the implementation of this part can go on, take some measures to ensure that the process running. Some teams used the "self-regulation" approach, ie Review work before submitting the code, then the case will be reflected in the changelog Review, for example:
The drawbacks of this approach is entirely dependent on the implementation of the norms of developers, if the couple appear or lack of self-discipline, then the Review work might not be implemented.
Code Review System
Code Review System is a method where the teams are using small series, which can effectively solve the problem of the implementation of the above specification, it probably workflow is as follows:
1. developers submit code . Code does not immediately enter the SVN repository, but will first be submitted to the Review board system.
2. Code of Diff view. Review other people have rights to view the content of submitted records Diff.
Click on the top right corner of View Diff, see what's changed.
3. Review by. If the code is not the problem, click Submit Ship it !, recorded in the upper right corner of the code by the Review automatically to the SVN repository.
Note: Some items are set to be more than n individuals (n can be configured) Review by the code only to the SVN repository.
4.Review not by asking questions . If the code is in doubt in Diff code interface, you can make notes on the lines of code in question, or submit a question.
The above is generally used in a method of code Review