How Useful is Code Change Information for Fault Localization in Continuous Integration?
The DOI matches its Crossref record; 8 of the 8 references it cites were found in a registry or an index.
Abstract
Continuous integration (CI) is the process in which code changes are automatically integrated, built, and tested in a shared repository. In CI, developers frequently merge and test code under development, which helps isolate faults with finer-grained change information. To identify faulty code, prior research has widely studied and evaluated the performance of spectrum-based fault localization (SBFL) techniques. While the continuous nature of CI requires the code changes to be atomic and presents fine-grained information on what part of the system is being changed, traditional SBFL techniques do not benefit from it. To overcome the limitation, we propose to integrate the code and coverage change information in fault localization under CI settings. First, code changes show how faults are introduced into the system, and provide developers with better understanding on the root cause. Second, coverage changes show how the code coverage is impacted when faults are introduced. This change information can help limit the search space of code coverage, which offers more opportunities for improving fault localization techniques. Based on the above observations, we propose three new change-based fault localization techniques, and compare them with Ochiai, a commonly used SBFL technique. We evaluate these techniques on 192 real faults from seven software systems. Our results show that all three change-based techniques outperform Ochiai on the Defects4J dataset. In particular, the improvement varies from 7% to 23% and 17% to 24% for average MAP and MRR, respectively. Moreover, we find that our change-based fault localization techniques can be integrated with Ochiai, and boost its performance by up to 53% and 52% for average MAP and MRR, respectively.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Defects4J: a database of existing faults to enable controlled testing studies for Java programs
Just, R., Jalali, D., & Ernst, M. D. (2014) · Proceedings of the 2014 International Symposium on Software Testing and Analysis · doi:10.1145/2610384.2628055 · Cited by 1,447
A Survey on Software Fault Localization
Wong, W. E., Gao, R., Li, Y., Abreu, R., & Wotawa, F. (2016) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2016.2521368 · Cited by 1,110 · cited 2×
“Prior studies [7, 9, 16, 17, 32, 58, 60] focused on studying the use of code coverage in locating faults under traditional software development settings.”
BackgroundUse of relative code churn measures to predict system defect density
Nagappan, N., & Ball, T. (2005) · Proceedings of the 27th international conference on Software engineering - ICSE '05 · doi:10.1145/1062455.1062514 · Cited by 775 · cited 1×
“We design CodeChange this way since we want to study how vanilla code changes may be used for fault localization, and previous research [38, 40, 59] observe that the size of a change is a good indicator of fault proneness.”
MethodShahin, M., Ali Babar, M., & Zhu, L. (2017) · IEEE Access · doi:10.1109/access.2017.2685629 · Cited by 680 · cited 2×
“Prior studies identify test failures as one of the main challenges in CI practices [13, 43].”
BackgroundUsage, costs, and benefits of continuous integration in open-source projects
Hilton, M., Tunnell, T., Huang, K., Marinov, D., & Dig, D. (2016) · Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/2970276.2970358 · Cited by 342
DeepFL: integrating multiple fault diagnosis dimensions for deep fault localization
Li, X., Li, W., Zhang, Y., & Zhang, L. (2019) · Proceedings of the 28th ACM SIGSOFT International Symposium on Software Testing and Analysis · doi:10.1145/3293882.3330574 · Cited by 336 · cited 1×
“Prior studies [33, 35, 44, 63, 64] have also demonstrated that such method level aggregation helps better distinguish the non-faulty statements from the faulty ones.”
BackgroundDevelopment and Deployment at Facebook
Feitelson, D. G., Frachtenberg, E., & Beck, K. L. (2013) · IEEE Internet Computing · doi:10.1109/mic.2013.25 · Cited by 243
Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy)
Neely, S., & Stolt, S. (2013) · 2013 Agile Conference · doi:10.1109/agile.2013.17 · Cited by 124
Research works printed but not linked: 56
- 2021. JaCoCo. https://www.eclemma.org/jacoco/. Last accessed May 5 2021.
- 2022. Deflaker. https://www.deflaker.org/. Last accessed February 28 2022.
- 2022. GZoltar. https://gzoltar.com/. Last accessed February 28 2022.
- Rui Abreu, Peter Zoeteweij, and Arjan J. C. van Gemund. 2009. Spectrum-Based Multiple Fault Localization. In Proceedings of the IEEE/ACM International Conference on Automated Software Engineering(ASE ’09). 88–99.
- 10.1016/j.jss.2009.06.035 · DOI · Paper page
- 10.1016/j.jss.2009.06.035 · DOI · Paper page
- 10.5555/1308173.1308264 · doi:10.5555/1308173.1308264
- Rui Abreu, Peter Zoeteweij, and Arjan J. C. van Gemund. 2007. On the Accuracy of Spectrum-based Fault Localization. In Proceedings of the Testing: Academic and Industrial Conference Practice and Research Techniques - MUTATION(TAICPART-MUTATION ’07). 89–98.
- 10.1109/ASE.2011.6100114 · DOI · Paper page
- Jonathan Bell, Owolabi Legunsen, Michael Hilton, Lamyaa Eloussi, Tifany Yung, and Darko Marinov. 2018. DeFlaker: Automatically detecting flaky tests. In 2018 IEEE/ACM 40th International Conference on Software Engineering (ICSE). IEEE, 433–444.
- 10.1109/MSR.2017.62 · DOI · Paper page
- 10.1145/2610384.2628058 · DOI · Paper page
- An Ran Chen, Tse-Hsun Peter Chen, and Shaowei Wang. 2021. Pathidea: Improving information retrieval-based bug localization by re-constructing execution paths using logs. IEEE Transactions on Software Engineering(2021).
- 10.1145/3338906.3338957 · DOI
- 10.1145/3324884.3416570 · DOI · Paper page
- 10.1109/ISSREW.2018.00005 · DOI
- Jackson Antonio do Prado Lima and Silvia Regina Vergilio. 2020. A multi-armed bandit approach for test case prioritization in continuous integration environments. IEEE Transactions on Software Engineering(2020).
- 10.1145/2635868.2635910 · DOI · Paper page
- 10.1109/TSE.2017.2755013 · DOI · Paper page
- 10.1145/3238147.3238183 · DOI
- [25] JavaParser.2019. https://javaparser.org/. Last accessed July 1 2020.
- 10.1109/ASE.2019.00054 · DOI · Paper page
- 10.1109/ICSE43902.2021.00069 · DOI · Paper page
- 10.1145/581396.581397 · DOI · Paper page
- 10.1145/2931037.2931051 · DOI · Paper page
- 10.1145/3106237.3106288 · doi:10.1145/3106237.3106288
- 10.1109/ICSM.2013.52 · DOI · Paper page
- 10.1109/ICSE43902.2021.00067 · DOI · Paper page
- 10.1145/3395363.3397351 · DOI · Paper page
- 10.1002/smr.1616 · DOI · Paper page
- 10.5555/1815297.1815299 · doi:10.5555/1815297.1815299
- 10.1145/1368088.1368114 · DOI · Paper page
- Manish Motwani and Yuriy Brun. 2020. Automatically repairing programs using both tests and bug reports. arXiv preprint arXiv:2011.08340(2020). · arXiv
- 10.1109/ICSE.2017.62 · DOI · Paper page
- 10.1145/3092703.3092717 · DOI · Paper page
- Xuezhi Song Yun Lin Siang Hwee Ng Ping Yu Xin Peng and Jin Song Dong. 2021. Constructing Regression Dataset from Code Evolution History. arXiv preprint arXiv:2109.12389(2021). · arXiv
- 10.1145/3001878.3001882 · doi:10.1145/3001878.3001882
- 10.1002/smr.1838 · DOI
- 10.1145/2786805.2786850 · DOI · Paper page
- 10.1145/2597008.2597148 · DOI · Paper page
- 10.1002/smr.1801 · DOI
- 10.1002/smr.1801 · DOI
- 10.1109/ICSE.2009.5070507 · DOI
- Ming Wen, Junjie Chen, Yongqiang Tian, Rongxin Wu, Dan Hao, Shi Han, and Shing-Chi Cheung. 2019. Historical spectrum based fault localization. IEEE Transactions on Software Engineering(2019).
- 10.1145/2970276.2970359 · DOI · Paper page
- 10.1145/3338906.3338962 · DOI · Paper page
- 10.1109/ICSME.2014.40 · DOI · Paper page
- 10.1016/j.jss.2009.09.037 · DOI · Paper page
- 10.1007/s10664-017-9567-4 · DOI
- 10.1145/2522920.2522924 · DOI · Paper page
- 10.1109/APSEC.2015.23 · DOI
- 10.1016/j.infsof.2020.106312 · DOI · Paper page
- 10.1145/3092703.3092731 · DOI · Paper page
- 10.1109/TSE.2019.2911283 · DOI · Paper page
- 10.5555/2337223.2337226 · doi:10.5555/2337223.2337226
- 10.1109/TSE.2019.2892102 · DOI · Paper page
Cited by
Towards Better Graph Neural Network-Based Fault Localization through Enhanced Code Representation
Rafi, M. N., Kim, D. J., Chen, A. R., Chen, T.-H. (., & Wang, S. (2024) · Proceedings of the ACM on Software Engineering · doi:10.1145/3660793 · Cited by 24
Self-citationRafi, M. N., Kim, D. J., Chen, T.-H., & Wang, S. (2024) · arXiv · doi:10.48550/arxiv.2412.18750
Self-citation
Metadata
- Authors
- Chen, A. R., Chen, T.-H. (., & Chen, J.
- Venue
- Proceedings of the 37th IEEE/ACM International Conference on Automated Software Engineering
- Publisher
- ACM
- Published
- 2022-10-10
- Pages
- 1-12
- Cited by
- 15
- References
- 8
- Funders
- National Natural Science Foundation of China (62002256)
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: How Useful is Code Change Information for Fault Localization in Continuous Integration? https://app.cochat.ai/papers/10.1145/3551349.3556931
- The paper
- Chen, A. R., Chen, T.-H. (., & Chen, J. (2022). How Useful is Code Change Information for Fault Localization in Continuous Integration? Proceedings of the 37th IEEE/ACM International Conference on Automated Software Engineering. https://doi.org/10.1145/3551349.3556931
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.