This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Test Cases: Is One Ever Enough?
January/February 2006 (vol. 8 no. 1)
pp. 44-48
Keith Miller, University of Illinois, Springfield
Surprisingly, some commercial software development departments use a ?one-test? policy when evaluating their software products. According to this policy, developers consider a software revision ready to go after only a single acceptance test. This policy flies in the face of not only common wisdom about testing, but also mathematical analyses of testing.
Index Terms:
one-test policy, mutation testing, metrics, faults, interface testing, reliability estimate, probability of failure (POF), fault size, software testing, debugging, simulations
Citation:
Keith Miller, Jeffrey Voas, "Software Test Cases: Is One Ever Enough?," IT Professional, vol. 8, no. 1, pp. 44-48, Jan.-Feb. 2006, doi:10.1109/MITP.2006.28
Usage of this product signifies your acceptance of the Terms of Use.