Cited by 48Software Engineering ResearchSoftware Engineering Techniques and PracticesSoftware Testing and Debugging Techniques

Code Review Automation: Strengths and Weaknesses of the State of the Art

Open access
Tufano, Rosalia, Dabić, Ozren, Mastropaolo, Antonio, Ciniselli, Matteo, Bavota, Gabriele·2024·IEEE Transactions on Software Engineering

Abstract

The automation of code review has been tackled by several researchers with the goal of reducing its cost. The adoption of deep learning in software engineering pushed the automation to new boundaries, with techniquesimitatingdevelopers in generative tasks, such as commenting on a code change as a reviewer would do or addressing a reviewer's comment by modifying code. The performance of these techniques is usually assessed through quantitative metrics,e.g.,the percentage of instances in the test set for which correct predictions are generated, leaving many open questions on the techniques’ capabilities. For example, knowing that an approach is able to correctly address a reviewer's comment in 10% of cases is of little value without knowing what was asked by the reviewer: What if in all successful cases the code change required to address the comment was just the removal of an empty line? In this paper we aim at characterizing the cases in which three code review automation techniques tend to succeed or fail in the two above-described tasks. The study has a strong qualitative focus, with$\sim$105 man-hours of manual inspection invested in manually analyzing correct and wrong predictions generated by the three techniques, for a total of 2,291 inspected predictions. The output of this analysis are two taxonomies reporting, for each of the two tasks, the types of code changes on which the experimented techniques tend to succeed or to fail, pointing to areas for future work. A result of our manual analysis was also the identification of several issues in the datasets used to train and test the experimented techniques. Finally, we assess the importance of researching in techniques specialized for code review automation by comparing their performance with ChatGPT, a general purpose large language model, finding that ChatGPT struggles in commenting code as a human reviewer would do.

Integrity signals

Registry

Crossref · 10.1109/tse.2023.3348172

Cites

52 of 52 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Recent assessments of automated code review report mixed results, noting that ChatGPT lacks skill in understanding the larger context of a program, as opposed to a small bit of code, as well as with making recommendations and implementing changes.

    “Recent assessments of the accuracy of automated code review report quite mixed results, noting that ChatGPT lacks skill in understanding the larger context of a program, as opposed to a small bit of a code, as well as with making recommendations and implementing changes (Tufano et al. 2024).”

    From Large language models and the problem of rhetorical debt (2025) · cites this paper as Tufano et al. 2024

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Tufano, R., Dabić, O., Mastropaolo, A., Ciniselli, M., & Bavota, G.
Affiliations
Università della Svizzera italiana (CH)
Venue
IEEE Transactions on Software Engineering
Published
2024-02
Volume
50
Issue
2
Pages
338-353
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
  • 2326-3881
OpenAlex
W4390480971
Cited by
48
References
52
Citations by year
2026: 16 · 2025: 26 · 2024: 6
FWCI
18.10
Type
journal article
Language
en
Open access
Locations
  • IEEE Transactions on Software Engineering (publishedVersion)
  • arXiv (Cornell University) (submittedVersion)
  • arXiv (Cornell University)
Funders
European Commission (HORIZON2020, 851720)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
Keywords
code review automation, code comment generation, dataset quality, ChatGPT, large language models

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review