Content deleted Content added
"debuging" should be "Debugging" |
Citation bot (talk | contribs) m Alter: title. Add: isbn, series, doi, chapter, pages, volume. Formatted dashes. | You can use this bot yourself. Report bugs here. | User-activated. |
||
Line 5:
}}
'''Delta Debugging''' is a methodology to automate the [[debugging]] of programs using a scientific approach of hypothesis-trial-result loop. This methodology was first developed by Andreas Zeller of the Saarland University in 1999.<ref>{{cite book|last1=Zeller|first1=Andreas|title=Software Engineering — ESEC/FSE '99|volume=1687|pages=253–267|chapter=Yesterday, my program worked. Today, it does not. Why?|date=1999|publisher=Springer|edition=Software Engineering—ESEC/FSE’99 [https://dx.doi.org/10.1007/3-540-48166-4_16 doi:10.1007/3-540-48166-4_16]|doi=10.1007/3-540-48166-4_16|series=Lecture Notes in Computer Science|isbn=978-3-540-66538-0}}</ref>
In practice, the Delta Debugging algorithm builds on [[unit testing]] to isolate failure causes automatically - by systematically narrowing down failure-inducing circumstances until a minimal set remains. For example, if you can supply a test case that will produce the bug you are looking for, then you can feed that to the Delta Debugging algorithm, which will then simply try to trim useless functions and lines of code that are not needed to reproduce the bug, until a 1-minimal program is found.
| |||