Revision as of 11:47, 22 July 2015 edit Signimu (talk \| contribs) Extended confirmed users 4,692 edits Extended description of bisect ← Previous edit		Revision as of 11:49, 22 July 2015 edit undo Signimu (talk \| contribs) Extended confirmed users 4,692 edits Added link for bisection Next edit →
Line 12: 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). Later, some software development tools have been inspired by Delta Debugging, such as the [[Bisection_(software_engineering)\|bisect commands]] of [[revision control]] systems (eg, 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. == Software ==

Delta debugging: Difference between revisions