Debugging with dynamic slicing and backtracking
Software—Practice & Experience
Experiments of the effectiveness of dataflow- and controlflow-based test adequacy criteria
ICSE '94 Proceedings of the 16th international conference on Software engineering
Visualization of test information to assist fault localization
Proceedings of the 24th International Conference on Software Engineering
An Execution Slice and Inter-Block Data Dependency-Based Approach for Fault Localization
APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
ICSM '05 Proceedings of the 21st IEEE International Conference on Software Maintenance
Empirical evaluation of the tarantula automatic fault-localization technique
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
A similarity-aware approach to testing based fault localization
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Testing-based interactive fault localization
Proceedings of the 28th international conference on Software engineering
Towards Interactive Fault Localization Using Test Information
APSEC '06 Proceedings of the XIII Asia Pacific Software Engineering Conference
Priority strategy of software fault localization
ACOS'07 Proceedings of the 6th Conference on WSEAS International Conference on Applied Computer Science - Volume 6
Accurately choosing execution runs for software fault localization
CC'06 Proceedings of the 15th international conference on Compiler Construction
Hi-index | 0.00 |
A dichotomy method is presented to perform on test-based fault localization. First the test information itself is optimized from three aspects: searching scope localization using slice technique, redundant test case removal, and test suite reduction with nearest series. Secondly, the diagnosis matrix is set up according to the optimized test information and each code is prioritized accordingly. Thirdly, dichotomy method is iteratively applied to an interactive process for seeking the bug: the searching scope is cut in two by the checkpoint cp, which is of the highest priority; If cpis wrong, the bug is found; else we will ignore the codes before/after it according to the result of cp. Finally, we conduct three studies with Siemens suite of 132 program mutants. Our method scores 0.85 on average, which means we only need to check less than 15% of the program before finding out a bug.