Content deleted Content added
→External links: Added Udacity course |
Cleanup. Notable. |
||
(47 intermediate revisions by 29 users not shown) | |||
Line 1:
{{Sources exist|date=January 2025}}
'''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 conference |last1=Zeller |first1=Andreas |book-title=Software Engineering — ESEC/FSE '99 |volume=1687 |pages=253–267 |title=Yesterday, my program worked. Today, it does not. Why?|date=1999 |publisher=Springer |doi=10.1007/3-540-48166-4_16 |series=Lecture Notes in Computer Science |isbn=978-3-540-66538-0}}</ref>
'''Delta Debugging''' automates the scientific method of [[debugging]]. The Delta Debugging algorithm isolates failure causes automatically - by systematically narrowing down failure-inducing circumstances until a minimal set remains. Delta Debugging has been applied to isolate failure-inducing program input (e.g. an HTML page that makes a Web browser fail), failure-inducing user interaction (e.g. the keystrokes that make a program crash), or failure-inducing changes to the program code (e.g. after a failing regression test).▼
The delta debugging algorithm isolates 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 trim lines of code that are not needed to reproduce the bug, until a 1-minimal program is found.
* [http://www.st.cs.uni-sb.de/eclipse/ Eclipse Plug-Ins]▼
▲
==References==▼
Software development tools inspired by delta debugging include the [[Bisection (software engineering)|bisect commands]] of [[revision control]] systems (e.g., git-bisect, svn-bisect, hg-bisect, etc.), which, instead of working on the program's code, apply the delta debugging methodology on the code history by comparing various versions until the faulty change is found.
==External links==▼
==See also==
* [[Bisection (software engineering)]]
* [[Program slicing]]
▲==References==
<references />
▲==External links==
[[Category:
|