Finding bugs by isolating unit tests

Authors:
Kivanç Muşlu;Bilge Soran;Jochen Wuttke
Affiliations:
University of Washington, Seattle, WA, USA;University of Washington, Seattle, WA, USA;University of Washington, Seattle, WA, USA
Venue:
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Year:
2011

Citing 4
Cited 2

Design for testability in object-oriented systems

Communications of the ACM
Prioritizing Test Cases For Regression Testing

IEEE Transactions on Software Engineering
A history-based test prioritization technique for regression testing in resource constrained environments

Proceedings of the 24th International Conference on Software Engineering
Software Testability: The New Verification

IEEE Software

Scaling up automated test generation: Automatically generating maintainable regression unit tests for programs

ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Integrating systematic exploration, analysis, and maintenance in software development

Proceedings of the 2013 International Conference on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

Even in simple programs there are hidden assumptions and dependencies between units that are not immediately visible in each involved unit. These dependencies are generally hard to identify and locate, and can lead to subtle faults that are often missed, even by extensive test suites. We propose to leverage existing test suites to identify faults due to hidden dependencies and to identify inadequate test suite design. Rather than just executing entire test suites within frameworks such as JUnit, we execute each test in isolation, thus removing masking effects that might be present in the test suites. We hypothesize that this can reveal previously hidden dependencies between program units or tests. A preliminary study shows that this technique is capable of identifying subtle faults that have lived in a system for 120 revisions, despite failures being reported and despite attempts to fix the fault.