A Survey on Software Fault Localization
By W. E. Wong, Ruizhi Gao, Yihao Li, Rui Abreu, Franz Wotawa. 2016
1,109 citations recorded by the source corpus.
Software fault localization, the act of identifying the locations of faults in a program, is widely recognized to be one of the most tedious, time consuming, and expensive - yet equally critical - activities in program debugging. Due to the increasing scale and complexity of software today, manually locating faults when failures occur is rapidly becoming infeasible, and consequently, there is a strong demand for techniques that can guide software developers to the locations of faults in a program with minimal human intervention. This demand in turn has fueled the proposal and development of a broad spectrum of fault localization techniques, each of which aims to streamline the fault localization process and make it more effective by attacking the problem in a unique way. In this article, we catalog and provide a comprehensive overview of such techniques and discuss key issues and concerns that are pertinent to software fault localization as a whole.
Subfields: Information Systems, Software, Program Analysis & Verification
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Charles Sutton
- Michael Pradel
- Miltiadis Allamanis
- Earl T. Barr
- Premkumar T. Devanbu
- Chun Xia
- Lingming Zhang
- Rishabh Singh
In Software
- Michael Pradel
- Charles Sutton
- Miltiadis Allamanis
- Earl T. Barr
- Chun Xia
- Lingming Zhang
- Premkumar T. Devanbu
- Koushik Sen
In Program Analysis & Verification
- Charles Sutton
- Michael Pradel
- Miltiadis Allamanis
- Aditya Kanade
- Earl T. Barr
- Premkumar T. Devanbu
- Satish Chandra
- Shirish K. Shevade
Citations in the corpus
- A Survey of Machine Learning for Big Code and Naturalness (2017, background): “systematically applied andyet suffer fromuncertainty problemsthat machinelearningis particularlywell suited to address, promising new advances. Debugging. Debugging isa commontask forsoftware engineers[191]. Debuggingislike trying tofindaneedleinthehaystack;adeveloperhastorecognizerelevantinformationf”
- Scaffle: bug localization on millions of files (2020, methodology): “Overall, Scaffle provides a practical technique for pinpointing the files to consider in a large-scale code base, which helps assigning crashes to the appropriate team or developer, and may serve as a starting point for automated program repair.”
- AutoCodeRover: Autonomous Program Improvement (2024, positive): “We note that the workflow of AutoCodeRover discussed so far only requires the problem statement 𝑃 and codebase 𝐶 as input, and do not require any program specifications such as testcases.”
- A Roadmap Toward the Resilient Internet of Things for Cyber-Physical Systems (2018, background): “This is often performed by root cause analysis [134] or fault-localization [135]–[141].”
- METHODS2TEST: A dataset of focal methods mapped to test cases (2022, background): “Examples of these tasks include automating developers’ activities, such as: bug-fixing [5, 27], fault localization [28], writing comments [13] and documentation [6], code reviews [25], and merge conflict resolution [24].”
- TBar: revisiting template-based automated program repair (2019, methodology): “s localized, ARP tools can mutate the buggy code entity to generate patches, which might fix a given bug. To identify defect locations in a program, several automated FL techniques have been proposed [67]: slice-based [41, 65], spectrum-based [3, 52], statisticsbased [28, 29], etc. Spectrum-based FL”
- Ask the Mutants: Mutating Faulty Programs for Fault Localization (2014, background): “A developer, then, is to inspect PUT following the order of statements in the given ranking, in the hope that the faulty statement will be encountered near the top of the ranking [26].”
- Practitioners' expectations on automated fault localization (2016, background): “, the proportion of time the success criterion is met) since they were measured in various ways to evaluate past fault localization techniques [14,28,49,51].”
- Agentless: Demystifying LLM-based Software Engineering Agents (2024, background): “Fault localization (FL) [90] techniques aim to identify the suspicious locations (e.g., statements or methods) in source code related to bugs.”
- Neural Attribution for Semantic Bug-Localization in Student Programs (2019, background): “Bug-localization is an active field of research in software engineering [29].”
- Fault Analysis and Debugging of Microservice Systems: Industrial Survey, Benchmark System, and Empirical Study (2018, background): “In addition, existing fault localization techniques [36] are ineffective for microservices.”
- SweRank: Software Issue Localization with Code Ranking (2025, unknown): “Traditional fault localization methods (Wong et al., 2016) can be grouped into spectrum-based and program-analysis approaches.”
- SweRank+: Multilingual, Multi-Turn Code Ranking for Software Issue Localization (2025, unknown): “A persistent bottleneck in this process is software issue localization (Wong et al., 2016): the task of identifying where in a codebase a fix should be applied for a given bug report or feature request.”
- IssueExec: A Test-Driven Approach for Localizing Software Engineering Issues (2026, unknown): “Given an issue description 𝑑 and the enriched test representations constructed in Section 4.2, IssueExec employs a two-phase filtering process that retrieves a subset T 𝑑 ⊆ T with |T 𝑑 | ≪ |T | while maximizing information extraction for downstream localization from the issue.”