Journal article · 2021 · Open access

Evaluating Automatic Program Repair Capabilities to Repair API Misuses

Maria Kechagia, Sergey Mechtaev, Federica Sarro, Mark Harman

IEEE Transactions on Software Engineering, 48(7), 2658–2679 · Published 18 March 2021 · DOI 10.1109/tse.2021.3067156

Open PDFView at the publisherCite this paper

In brief

“Evaluating Automatic Program Repair Capabilities to Repair API Misuses” is a 2021 journal article by Maria Kechagia and 3 co-authors, published in IEEE Transactions on Software Engineering. OpenAlex counts 43 citations as of 19 November 2026, which puts it in the top 4% of works published in 2021 by citations. It is open access: the full text is free to read at UCL Discovery (University College London).

Citations
43
Most cited in
2024 (13)
Field-weighted impact
6.15
References
91
Authors
4

Abstract

API misuses are well-known causes of software crashes and security vulnerabilities. However, their detection and repair is challenging given that the correct usages of (third-party)apis might be obscure to the developers of client programs. This paper presents the first empirical study to assess the ability of existing automated bug repair tools to repairapimisuses, which is a class of bugs previously unexplored. Our study examines and compares 14 Java test-suite-based repair tools (11 proposed before 2018, and three afterwards) on a manually curated benchmark (APIRepBench) consisting of 101apimisuses. We develop an extensible execution framework (APIARTy) to automatically execute multiple repair tools. Our results show that the repair tools are able to generate patches for 28 percent of theapimisuses considered. While the 11 less recent tools are generally fast (the median execution time of the repair attempts is 3.87 minutes and the mean execution time is 30.79 minutes), the three most recent are less efficient (i.e., 98 percent slower) than their predecessors. The tools generate patches forapimisuses that mostly belong to the categories of missingnullcheck, missing value, missing exception, and missing call. Most of the patches generated by all tools are plausible (65 percent), but only few of these patches are semantically correct to human patches (25 percent). Our findings suggest that the design of future repair tools should support the localisation of complex bugs, including different categories ofapimisuses, handling of timeout issues, and ability to configure large software projects. BothAPIRepBenchandAPIARTyhave been made publicly available for other researchers to evaluate the capabilities of repair tools on detecting and fixingapimisuses.

Cite this paper

Formatted from the catalogue record. Check names, capitals and page numbers against the paper before you submit.

APA 7

Kechagia, M., Mechtaev, S., Sarro, F., & Harman, M. (2021). Evaluating Automatic Program Repair Capabilities to Repair API Misuses. IEEE Transactions on Software Engineering, 48(7), 2658–2679. https://doi.org/10.1109/tse.2021.3067156

MLA 9

Kechagia, Maria, et al. “Evaluating Automatic Program Repair Capabilities to Repair API Misuses.” IEEE Transactions on Software Engineering, vol. 48, no. 7, 2021, pp. 2658–2679. https://doi.org/10.1109/tse.2021.3067156.

Chicago

Kechagia, Maria, Sergey Mechtaev, Federica Sarro, and Mark Harman. 2021. “Evaluating Automatic Program Repair Capabilities to Repair API Misuses.” IEEE Transactions on Software Engineering 48 (7): 2658–2679. https://doi.org/10.1109/tse.2021.3067156.

Harvard

Kechagia, M. et al. (2021) ‘Evaluating Automatic Program Repair Capabilities to Repair API Misuses’, IEEE Transactions on Software Engineering, 48(7), pp. 2658–2679. doi:10.1109/tse.2021.3067156.

IEEE

M. Kechagia, S. Mechtaev, F. Sarro, and M. Harman, “Evaluating Automatic Program Repair Capabilities to Repair API Misuses,” IEEE Transactions on Software Engineering, vol. 48, no. 7, pp. 2658–2679, 2021, doi: 10.1109/tse.2021.3067156.

BibTeX

@article{kechagia2021evaluating,
  title     = {{Evaluating Automatic Program Repair Capabilities to Repair API Misuses}},
  author    = {Kechagia, Maria and Mechtaev, Sergey and Sarro, Federica and Harman, Mark},
  journal   = {IEEE Transactions on Software Engineering},
  year      = {2021},
  volume    = {48},
  number    = {7},
  pages     = {2658--2679},
  doi       = {10.1109/tse.2021.3067156},
  url       = {https://doi.org/10.1109/tse.2021.3067156}
}

Download for a reference manager: BibTeX (.bib) · RIS for Zotero, Mendeley and EndNote (.ris)

Citations by year

YearCitationsShare of the best year
202155
202288
202377
20241313
202566
202644

Its field-weighted citation impact is 6.15: it has been cited 6.15 times as often as the average work of the same field, type and year (1.00 is the world average).

Topic and keywords

Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques

  • automated program repair
  • API misuse
  • Java
  • exception handling
  • software crashes
  • security vulnerabilities

Work with this paper

Most-cited papers in Computer Science

All highly cited Computer Science papers

Questions about this paper

How do I cite this paper in APA style?

Kechagia, M., Mechtaev, S., Sarro, F., & Harman, M. (2021). Evaluating Automatic Program Repair Capabilities to Repair API Misuses. IEEE Transactions on Software Engineering, 48(7), 2658–2679. https://doi.org/10.1109/tse.2021.3067156

How many times has this paper been cited?

43 times, according to OpenAlex on 19 November 2026. Google Scholar and Scopus count different sets of sources, so their numbers differ.

Is this paper free to read?

Yes. It is open access at UCL Discovery (University College London): sign in and open the PDF from this page.

Who wrote this paper?

Maria Kechagia, Sergey Mechtaev, Federica Sarro, Mark Harman.

What is the DOI of this paper?

10.1109/tse.2021.3067156, permanently at https://doi.org/10.1109/tse.2021.3067156. Sign in and open it from this page.

Bibliographic data from OpenAlex (CC0), last checked 19 November 2026. ResearchGuru does not host this paper; once you are signed in, the links open it at the publisher or the repository that does.