Simplifying and Isolating Failure-Inducing Input

By Andreas Zeller, Ralf Hildebrandt. IEEE Trans. Software Eng., 2002

1,225 citations recorded by the source corpus.

Subfields: Information Systems, Software, Signal Processing

View Paper: https://www.semanticscholar.org/paper/a397c5d4fadcc0ce29123b78815987b543417ba4

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

In Software

In Signal Processing

Citations in the corpus

BugFix: A learning-based tool to assist developers in fixing bugs (2009, background): “In the Delta Debugging framework, failure-inducing input is identified [33] that allows for the computation of cause-effect chains for failures [32] which can in turn be linked to faulty code [6].”
Precimonious: Tuning assistant for floating-point precision (2013, methodology): “Delta-Debugging: The delta-debugging search algorithm [29] ﬁnds a 1-minimal test case with the average running time of O ( n log n ).”
Mining version histories to guide software changes (2004, background): “Adopting the notation from [26], a change is a mapping δ : P → P , which, when applied, transforms a product p ∈ P into a changed product”
Fault localization with nearest neighbor queries (2003, background): “Zeller [29] extended these input minimizing techniques to handle cases where there is no monotonicity, while giving weaker guarantees on the minimality of the input.”
Automatic patch generation by learning correct code (2016, methodology): “We use a geometric distribution for the defect localization information because previous defect localization work reports that statements with higher localization ranks are significantly more likely to be patched than statements with lower localization ranks [11, 37].”
The DStar Method for Effective Software Fault Localization (2014, methodology): “This is an extension of their earlier work with delta debugging [49].”
Locating causes of program failures (2005, methodology): “Delta Debugging [16] is a general procedure to obtain such a small subset.”
Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports (2012, neutral): “There are also other techniques that help developers automatically locate bugs, such as delta debugging [39] and dynamic slicing [38].”
Evaluating and Improving Fault Localization (2017, methodology): “Defects4J’s patch minimization was performed by three authors of this paper, using both automated analysis (such as delta debugging [50]) and manual analysis to ﬁnd a minimal patch that they agreed preserved the spirit of the programmer’s ﬁx.”
Search-Based Software Testing: Past, Present and Future (2011, methodology): “[53] have investigated minimizing unit tests using an approach based on Delta-Debugging [54], which is used to identify ineffectual statements in the test case.”
Metallaxis‐FL: mutation‐based fault localization (2015, methodology): “This method recognizes and isolates input parts responsible for failures [6], recognizes chains of program states that lead to the failure [5] and links these chains with the faulty code.”
A Survey on Software Fault Localization (2016, methodology): “and Hildebrandt propose a technique, delta debugging [400], [401], by contrasting program states between executions of a successful test and a failed test via their memory graphs which are described in [426].”
Fuzzing with Code Fragments (2012, methodology): “To determine which individual tests are relevant for failure reproduction we use the delta debugging algorithm [24] and the delta tool [9] to filter out irrelevant test cases.”
Is the cure worse than the disease? overfitting in automated program repair (2015, methodology): “GenProg uses patch minimization, via delta debugging [63], to reduce code bloat.”
Automated feedback generation for introductory programming assignments (2012, methodology): “Techniques like Delta Debugging [44] and QuickXplain [26] aim to simplify a failing test case to a minimal test case that still exhibits the same failure.”
Test-case reduction for C compiler bugs (2012, methodology): “Zeller and Hildebrandt [18] developed delta debugging in 2002 and instantiated it in the dd and ddmin algorithms.”