PLDI '90 Proceedings of the ACM SIGPLAN 1990 conference on Programming language design and implementation
An empirical study of the reliability of UNIX utilities
Communications of the ACM
Critical slicing for software fault localization
ISSTA '96 Proceedings of the 1996 ACM SIGSOFT international symposium on Software testing and analysis
7th SIGSOFT Symposium on Foundations of Software Engineering together with 7th European Software Engineering Conference
Yesterday, my program worked. Today, it does not. Why?
ESEC/FSE-7 Proceedings of the 7th European software engineering conference held jointly with the 7th ACM SIGSOFT international symposium on Foundations of software engineering
An efficient relevant slicing method for debugging
ESEC/FSE-7 Proceedings of the 7th European software engineering conference held jointly with the 7th ACM SIGSOFT international symposium on Foundations of software engineering
Programmers use slices when debugging
Communications of the ACM
Massive Stochastic Testing of SQL
VLDB '98 Proceedings of the 24rd International Conference on Very Large Data Bases
The impact of test suite granularity on the cost-effectiveness of regression testing
Proceedings of the 24th International Conference on Software Engineering
Automated Debugging: Are We Close
Computer
Automated support for classifying software failure reports
Proceedings of the 25th International Conference on Software Engineering
Mutation analysis to verify feature matrices for isolating errors in simulation models
ACSC '03 Proceedings of the 26th Australasian computer science conference - Volume 16
The data mining approach to automated software testing
Proceedings of the ninth ACM SIGKDD international conference on Knowledge discovery and data mining
ISSTA '04 Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis
A Statistical Model to Locate Faults at Input Level
Proceedings of the 19th IEEE international conference on Automated software engineering
On test suite composition and cost-effective regression testing
ACM Transactions on Software Engineering and Methodology (TOSEM)
Experimental evaluation of using dynamic slices for fault location
Proceedings of the sixth international symposium on Automated analysis-driven debugging
Simulation-based bug trace minimization with BMC-based refinement
ICCAD '05 Proceedings of the 2005 IEEE/ACM International conference on Computer-aided design
Pruning dynamic slices with confidence
Proceedings of the 2006 ACM SIGPLAN conference on Programming language design and implementation
Locating faults through automated predicate switching
Proceedings of the 28th international conference on Software engineering
Carving differential unit test cases from system test cases
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
A study of effectiveness of dynamic slicing in locating real faults
Empirical Software Engineering
Locating faulty code by multiple points slicing
Software—Practice & Experience
An approach to detecting duplicate bug reports using natural language and execution information
Proceedings of the 30th international conference on Software engineering
Debugging strategies for mere mortals
Proceedings of the 46th Annual Design Automation Conference
Software testing with QuickCheck
CEFP'09 Proceedings of the Third summer school conference on Central European functional programming school
QuickCheck testing for fun and profit
PADL'07 Proceedings of the 9th international conference on Practical Aspects of Declarative Languages
Fundamentals of debugging using a resolution calculus
FASE'06 Proceedings of the 9th international conference on Fundamental Approaches to Software Engineering
| Hi-index | 0.00 |
Given some test case, a program fails. Which part of the test case is responsible for the particular failure? We show how our delta debugging algorithm generalizes and simplifies some failing input to a minimal test case that produces the failure.In a case study, the Mozilla web browser crashed after 95 user actions. Our prototype implementation automatically simplified the input to 3 relevant user actions. Likewise, it simplified 896~lines of HTML to the single line that caused the failure. The case study required 139 automated test runs, or 35 minutes on a 500 MHz PC.