ACM Home Page
Please provide us with feedback. Feedback
Experimental assessment of random testing for object-oriented software
Full text PdfPdf (818 KB)
Source
International Symposium on Software Testing and Analysis archive
Proceedings of the 2007 international symposium on Software testing and analysis table of contents
London, United Kingdom
SESSION: Empirical studies of testing approaches table of contents
Pages: 84 - 94  
Year of Publication: 2007
ISBN:978-1-59593-734-6
Authors
Ilinca Ciupa  Swiss Federal Institute of Technology
Andreas Leitner  Swiss Federal Institute of Technology
Manuel Oriol  Swiss Federal Institute of Technology
Bertrand Meyer  Swiss Federal Institute of Technology
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 57,   Downloads (12 Months): 281,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1273463.1273476
What is a DOI?

ABSTRACT

Progress in testing requires that we evaluate the effectiveness of testing strategies on the basis of hard experimental evidence, not just intuition or a priori arguments. Random testing, the use of randomly generated test data, is an example of a strategy that the literature often deprecates because of such preconceptions. This view is worth revisiting since random testing otherwise offers several attractive properties: simplicity of implementation, speed of execution, absence of human bias.

We performed an intensive experimental analysis of the efficiency of random testing on an existing industrial-grade code base. The use of a large-scale cluster of computers, for a total of 1500 hours of CPU time, allowed a fine-grain analysis of the individual effect of the various parameters involved in the random testing strategy, such as the choice of seed for a random number generator. The results provide insights into the effectiveness of random testing and a number of lessons for testing researchers and practitioners.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
The EiffelBase library. Eiffel Software Inc. http://www.eiffel.com/.
 
2
Jtest. Parasoft Corporation. http://www.parasoft.com/.
 
3
J. H. Andrews, S. Haldar, Y. Lei, and C. H. Li. Randomized unit testing: Tool support and best practices. Technical Report 663, Department of Computer Science, University of Western Ontario, January 2006.
4
5
6
 
7
T. Y. Chen, H. Leung, and I. K. Mak. Adaptive random testing. In M. J. Maher, editor, Advances in Computer Science - ASIAN 2004: Higher-Level Decision Making. 9th Asian Computing Science Conference. Proceedings. Springer-Verlag GmbH, 2004.
8
 
9
 
10
I. Ciupa and A. Leitner. Automatic testing based on Design by Contract. In Proceedings of Net.ObjectDays 2005 (6th Annual International Conference on Object-Oriented and Internet-based Technologies, Concepts, and Applications for a Networked World), pages 545--557, September 19-22 2005.
11
 
12
 
13
 
14
J. Duran and S. Ntafos. An evaluation of random testing. IEEE Transactions on Software Engineering, SE-10:438--444, July 1984.
15
16
 
17
 
18
R. Hamlet. Random testing. In J. Marciniak, editor, Encyclopedia of Software Engineering, pages 970--978. Wiley, 1994.
 
19
 
20
 
21
 
22
C. Oriat. Jartege: a tool for random generation of unit tests for Java classes. Technical Report RR-1069-I, Centre National de la Recherche Scientifique, Institut National Polytechnique de Grenoble, Universite Joseph Fourier Grenoble I, June 2004.
 
23
C. Pacheco and M. D. Ernst. Eclat: Automatic generation and classification of test inputs. In ECOOP 2005 - Object-Oriented Programming, 19th European Conference, Glasgow, Scotland, July 25-29, 2005.
 
24



REVIEW

"Andrew Brooks : Reviewer"

The testing tool AutoTest uses contracts in Eiffel code as an oracle, with random test inputs generated automatically. Such testing, though, lacks determinism. How often should void methods be called to force objects into more interesting states (  more...

Collaborative Colleagues:
Ilinca Ciupa: colleagues
Andreas Leitner: colleagues
Manuel Oriol: colleagues
Bertrand Meyer: colleagues