This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
What Is Software Testing? And Why Is It So Hard?
January/February 2000 (vol. 17 no. 1)
pp. 70-79
ASCII Text
x 
 
James A. Whittaker, "What Is Software Testing? And Why Is It So Hard?," IEEE Software, vol. 17, no. 1, pp. 70-79, January/February, 2000.
 
 
BibTex
x
 
@article{ 10.1109/52.819971,
author = {James A. Whittaker},
title = {What Is Software Testing? And Why Is It So Hard?},
journal ={IEEE Software},
volume = {17},
number = {1},
issn = {0740-7459},
year = {2000},
pages = {70-79},
doi = {http://doi.ieeecomputersociety.org/10.1109/52.819971},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - What Is Software Testing? And Why Is It So Hard?
IS - 1
SN - 0740-7459
SP70
EP79
EPD - 70-79
A1 - James A. Whittaker,
PY - 2000
VL - 17
JA - IEEE Software
ER -
 
The author sheds some light on why testing today's software products is so challenging, and he identifies several solid approaches that all testers should be able to thoughtfully apply. The effective tester has a rich toolkit of fundamental testing techniques, understands how the product will be used in its operating environment, and has a nose for where subtle bugs might lurk in the product and a bag of tricks for flushing them out. The methods described here can help testers provide a sensible answer to the question of what they really mean when they say they are done testing a software system.
Citation:
James A. Whittaker, "What Is Software Testing? And Why Is It So Hard?," IEEE Software, vol. 17, no. 1, pp. 70-79, Jan.-Feb. 2000, doi:10.1109/52.819971
Usage of this product signifies your acceptance of the Terms of Use.