Information Processing Letters
Programmers use slices when debugging
Communications of the ACM
Software reliability methods
Simplifying and Isolating Failure-Inducing Input
IEEE Transactions on Software Engineering
Art of Software Testing
Automated Software Engineering
PSE: explaining program failures via postmortem static analysis
Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
HDD: hierarchical delta debugging
Proceedings of the 28th international conference on Software engineering
Fast and simple XML tree differencing by sequence alignment
Proceedings of the 2006 ACM symposium on Document engineering
A Tool Platform Using an XML Representation of Source Code Information
IEICE - Transactions on Information and Systems
Evolutionary repair of faulty software
Applied Soft Computing
Hi-index | 0.00 |
Automated debugging attempts to locate the reason for a failure. Delta debugging minimizes the difference between two inputs, where one input is processed correctly while the other input causes a failure, using a series of test runs to determine the outcome of applied changes. Delta debugging is applicable to inputs or to the program itself, as long as a correct version of the program exists. However, complex errors are often masked by other program defects, making it impossible to obtain a correct version of the program through delta debugging in such cases. Iterative delta debugging extends delta debugging and removes series of defects step by step, until the final unresolved defect alone is isolated. The method is automated and managed to localize a bug in some real-life examples.