Answers are grounded in this paper and cite their sources.
Code review is advocated as one of the best practices to improve software quality and reduce the likelihood of introducing defects during code change activities. Recent research has shown how code components having a high review coverage (i.e., a high proportion of reviewed changes) tend to be less involved in post-release fixing activities. Yet the relationship between code review and bug introduction or the overall software quality is still largely unexplored.
No takes yet. Share an insight, caveat, or question.
Bavota et al. (2015) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: