Basic Concepts and Taxonomy of Dependable and Secure Computing
IEEE Transactions on Dependable and Secure Computing
Empirical evaluation of the tarantula automatic fault-localization technique
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Statistical Debugging: A Hypothesis Testing-Based Approach
IEEE Transactions on Software Engineering
Diagnosis of Embedded Software Using Program Spectra
ECBS '07 Proceedings of the 14th Annual IEEE International Conference and Workshops on the Engineering of Computer-Based Systems
On the Accuracy of Spectrum-based Fault Localization
TAICPART-MUTATION '07 Proceedings of the Testing: Academic and Industrial Conference Practice and Research Techniques - MUTATION
A Crosstab-based Statistical Method for Effective Fault Localization
ICST '08 Proceedings of the 2008 International Conference on Software Testing, Verification, and Validation
Information Foraging Theory: Adaptive Interaction with Information
Information Foraging Theory: Adaptive Interaction with Information
VIDA: Visual interactive debugging
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Common Trends in Software Fault and Failure Data
IEEE Transactions on Software Engineering
A practical evaluation of spectrum-based fault localization
Journal of Systems and Software
EZUNIT: a framework for associating failed unit tests with potential programming errors
XP'07 Proceedings of the 8th international conference on Agile processes in software engineering and extreme programming
Prioritizing Tests for Software Fault Localization
QSIC '10 Proceedings of the 2010 10th International Conference on Quality Software
Automating GUI testing for Android applications
Proceedings of the 6th International Workshop on Automation of Software Test
Experiences of System-Level Model-Based GUI Testing of an Android Application
ICST '11 Proceedings of the 2011 Fourth IEEE International Conference on Software Testing, Verification and Validation
Using GUI ripping for automated testing of Android applications
Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering
GZoltar: an eclipse plug-in for testing and debugging
Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering
Software Fault Localization Using DStar (D*)
SERE '12 Proceedings of the 2012 IEEE Sixth International Conference on Software Security and Reliability
Automated concolic testing of smartphone apps
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
An Information Foraging Theory Perspective on Tools for Debugging, Refactoring, and Reuse Tasks
ACM Transactions on Software Engineering and Methodology (TOSEM)
How Programmers Debug, Revisited: An Information Foraging Theory Perspective
IEEE Transactions on Software Engineering
Proceedings of the 2013 International Symposium on Software Testing and Analysis
GROPG: a graphical on-phone debugger
Proceedings of the 2013 International Conference on Software Engineering
Run-time adaptation of mobile applications using genetic algorithms
Proceedings of the 8th International Symposium on Software Engineering for Adaptive and Self-Managing Systems
MFL: Method-Level Fault Localization with Causal Inference
ICST '13 Proceedings of the 2013 IEEE Sixth International Conference on Software Testing, Verification and Validation
| Hi-index | 0.00 |
Automated diagnosis of errors and/or failures detected during software testing can greatly improve the efficiency of the debugging process, and thus help to make applications more reliable. In this paper, we propose an approach, dubbed MZoltar, offering dynamic analysis (namely, spectrum-based fault localization) of mobile apps that produces a diagnostic report to help identifying potential defects quickly. The approach also offers a graphical representation of the diagnostic report, making it easier to understand. Our experimental results show that the approach requires low runtime overhead (5.75% on average), while the tester needs to inspect 5 components (statements in this paper) on average to find the fault.