Editing Code review (section)

{{short description|Activity where one or more people check a program's code}}
{{Software development process}}
[[File:Pair_Programming_3.jpg | thumb|220x124px | right | Software Engineers ({{Aka}} programmers) reviewing a program]]
'''Code review''' (sometimes referred to as [[Software peer review|peer review]]) is a [[software quality assurance]] activity in which one or more people examine the [[source code]] of a [[computer program]], either after implementation or during the development process. The persons performing the checking, excluding the author, are called "reviewers". At least one reviewer must not be the code's author.<ref name="baum2016qrs">{{cite book |last1=Baum |first1=Tobias |last2=Liskin |first2=Olga |last3=Niklas |first3=Kai |last4=Schneider |first4=Kurt |title= 2016 IEEE International Conference on Software Quality, Reliability and Security (QRS)|pages=74–85 |date=2016 |doi=10.1109/QRS.2016.19|isbn=978-1-5090-4127-5 |chapter=A Faceted Classification Scheme for Change-Based Industrial Code Review Processes |s2cid=9569007 }}</ref><ref name="best_practices">{{cite book | last = Kolawa | first = Adam |author2=Huizinga, Dorota | title = Automated Defect Prevention: Best Practices in Software Management | url = http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html | year = 2007 | publisher = Wiley-IEEE Computer Society Press | page=260 | isbn = 978-0-470-04212-0 }}</ref>

Code review differs from related [[software quality assurance]] techniques like [[static code analysis]], [[Rubber duck debugging|self-checks]], [[Software testing|testing]], and [[pair programming]]. Static analysis relies primarily on automated tools, self-checks involve only the author, testing requires code execution, and pair programming is performed continuously during development rather than as a separate step.<ref name="baum2016qrs"/>