Yesterday, my program worked. Today, it does not. Why?
- ESEC 1999
by
Andreas Zeller
Oscar Nierstrasz, M. Lemoine (Ed.), Proceedings of the ESEC/FSE'99, 7th European Software Engineering Conference, Pages 253-267, Lecture Notes in Computer Science, Volume 1687, Springer, September 1999.
ISBN: 3540665382
Digital Library via DOI: 10.1145/318773.318946 - Local copy: Download as PDF file.
See also
More information is available at http://www.st.cs.uni-saarland.de/dd/.
Abstract
Imagine some program and a number of changes. If none of these changes is applied ("yesterday"), the program works. If all changes are applied ("today"), the program does not work. Which change is responsible for the failure? We present an efficient algorithm that determines the minimal set of failure-inducing changes. Our delta debugging prototype tracked down a single failure-inducing change from 178,000 changed GDB lines within a few hours.
Keywords
- testing and test tools
- regression testing
- debugging
BibTeX Entry
@inproceedings{zeller-esec-1999,
title = "Yesterday, my program worked. Today, it does not. Why?",
author = "Andreas Zeller",
year = "1999",
month = sep,
booktitle = "Proceedings of the ESEC/FSE'99, 7th European Software Engineering Conference",
editors = "Oscar Nierstrasz and M. Lemoine",
location = "Toulouse, France",
pages = "253--267",
publisher = "Springer",
series = "Lecture Notes in Computer Science",
volume = "1687",
ISBN = "3540665382",
doi = "10.1145/318773.318946",
}