|
| 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
| ASCII Text | x | ||
| Keith Miller, Jeffrey Voas, "Software Test Cases: Is One Ever Enough?," IT Professional, vol. 8, no. 1, pp. 44-48, January/February, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MITP.2006.28, author = {Keith Miller and Jeffrey Voas}, title = {Software Test Cases: Is One Ever Enough?}, journal ={IT Professional}, volume = {8}, number = {1}, issn = {1520-9202}, year = {2006}, pages = {44-48}, doi = {http://doi.ieeecomputersociety.org/10.1109/MITP.2006.28}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IT Professional TI - Software Test Cases: Is One Ever Enough? IS - 1 SN - 1520-9202 SP44 EP48 EPD - 44-48 A1 - Keith Miller, A1 - Jeffrey Voas, PY - 2006 KW - one-test policy KW - mutation testing KW - metrics KW - faults KW - interface testing KW - reliability estimate KW - probability of failure (POF) KW - fault size KW - software testing KW - debugging KW - simulations VL - 8 JA - IT Professional ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MITP.2006.28
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.