EUVIMEDEUVIMED entdecken
Crossref

Code-line-level Bugginess Identification: How Far have We Come, and How Far have We Yet to Go?

Zhaoqiang Guo, Shiran Liu, Xutong Liu, Wei Lai, Mingliang Ma, Xu Zhang, Chao Ni, Yibiao Yang, Yanhui Li, Lin Chen, Guoqiang Zhou, Yuming Zhou

ACM Transactions on Software Engineering and Methodology · 31.10.2023 · 32 (4) · 1-55

DOI: 10.1145/3582572 ↗

Kurz gefasst

Fachartikel in der Zeitschrift ACM Transactions on Software Engineering and Methodology, online erschienen am 27.05.2023. Verfasst von Zhaoqiang Guo und 11 weiteren Autor:innen. Die Arbeit wurde bisher 17-mal zitiert (Crossref) und nennt 88 Literaturangaben.

AbstractBibliografische AngabenZitierenVerwandte Studien

Abstract (Originalsprache)

Background

Code-line-level bugginess identification (CLBI) is a vital technique that can facilitate developers to identify buggy lines without expending a large amount of human effort. Most of the existing studies tried to mine the characteristics of source codes to train supervised prediction models, which have been reported to be able to discriminate buggy code lines amongst others in a target program. Problem. However, several simple and clear code characteristics, such as complexity of code lines, have been disregarded in the current literature. Such characteristics can be acquired and applied easily in an unsupervised way to conduct more accurate CLBI, which also can decrease the application cost of existing CLBI approaches by a large margin.

Objective

We aim at investigating the status quo in the field of CLBI from the perspective of (1) how far we have really come in the literature, and (2) how far we have yet to go in the industry, by analyzing the performance of state-of-the-art (SOTA) CLBI approaches and tools, respectively.

Method

We propose a simple heuristic baseline solution GLANCE (aimin G at contro L - AN d C ompl E x-statements) with three implementations (i.e., GLANCE-MD, GLANCE-EA, and GLANCE-LR). GLANCE is a two-stage CLBI framework: first, use a simple model to predict the potentially defective files; second, leverage simple code characteristics to identify buggy code lines in the predicted defective files. We use GLANCE as the baseline to investigate the effectiveness of the SOTA CLBI approaches, including natural language processing (NLP) based, model interpretation techniques (MIT) based, and popular static analysis tools (SAT).

Result

Based on 19 open-source projects with 142 different releases, the experimental results show that GLANCE framework has a prediction performance comparable or even superior to the existing SOTA CLBI approaches and tools in terms of 8 different performance indicators.

Conclusion

The results caution us that, if the identification performance is the goal, the real progress in CLBI is not being achieved as it might have been envisaged in the literature and there is still a long way to go to really promote the effectiveness of static analysis tools in industry. In addition, we suggest using GLANCE as a baseline in future studies to demonstrate the usefulness of any newly proposed CLBI approach.

Zitieren

APA

Guo, Z., Liu, S., Liu, X., Lai, W., Ma, M., Zhang, X., Ni, C., Yang, Y., Li, Y., Chen, L., Zhou, G., & Zhou, Y. (2023). Code-line-level Bugginess Identification: How Far have We Come, and How Far have We Yet to Go?. ACM Transactions on Software Engineering and Methodology, 32(4), 1-55. https://doi.org/10.1145/3582572

Vancouver

Guo Z, Liu S, Liu X, Lai W, Ma M, Zhang X, et al. Code-line-level Bugginess Identification: How Far have We Come, and How Far have We Yet to Go?. ACM Transactions on Software Engineering and Methodology. 2023;32(4):1-55. doi:10.1145/3582572

BibTeX
@article{Guo2023,
  author = {Guo, Zhaoqiang and Liu, Shiran and Liu, Xutong and Lai, Wei and Ma, Mingliang and Zhang, Xu and Ni, Chao and Yang, Yibiao and Li, Yanhui and Chen, Lin and Zhou, Guoqiang and Zhou, Yuming},
  title = {Code-line-level Bugginess Identification: How Far have We Come, and How Far have We Yet to Go?},
  journal = {ACM Transactions on Software Engineering and Methodology},
  year = {2023},
  volume = {32},
  number = {4},
  pages = {1--55},
  doi = {10.1145/3582572}
}
Kostenlos starten →