Partition Testing Does Not Inspire Confidence (Program Testing)
IEEE Transactions on Software Engineering
Analyzing Partition Testing Strategies
IEEE Transactions on Software Engineering
Simulating the Behavior of Software Modules by Trace Rewriting
IEEE Transactions on Software Engineering
The ASTOOT approach to testing object-oriented programs
ACM Transactions on Software Engineering and Methodology (TOSEM)
ClassBench: a framework for automated class testing
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
Partition Testing vs. Random Testing: The Influence of Uncertainty
IEEE Transactions on Software Engineering
Broad-spectrum studies of log file analysis
Proceedings of the 22nd international conference on Software engineering
An Experimental Comparison of the Effectiveness of Branch Testing and Data Flow Testing
IEEE Transactions on Software Engineering
Programmatic Testing of the Standard Template Library Containers
ASE '98 Proceedings of the 13th IEEE international conference on Automated software engineering
General Test Result Checking with Log File Analysis
IEEE Transactions on Software Engineering
An Evaluation of Random Testing
IEEE Transactions on Software Engineering
Hi-index | 0.00 |
We study coverage-checked random unit testing (CRUT), the practice of repeatedly testing units on sequences of random function calls until given code coverage goals are achieved. Previous research has shown that this practice can be a useful complement to traditional testing methods. However, questions remained as to the breadth of its applicability. In this paper, we report on a case study in which we applied CRUT to the testing of two mature public-domain data structures packages. We show that CRUT helped in identifying faults, in debugging, in extracting and specifying actual behaviour, and in achieving greater assurance of the correctness of the debugged software.