Software testing is arguably the least understood part of the development process. Through a four-phase approach, the author shows why eliminating bugs is tricky and why testing is a constant trade-off. James A. Whittaker, Florida Institute of Technology V
feature

practice tutorial
Testing? And WhyIs It So Hard?
Software testing isJames A. Whittaker, Florida Institute of Technologyarguably the leastunderstood part of
irtually all developers know the frustration of having softwarethe development
process. Throughbugs reported by users. When this happens, developers inevitably
a four-phaseask: How did those bugs escape testing? Countless hours doubt-approach, the
less went into the careful testing of hundreds or thousands ofauthor shows why
eliminating bugsvariables and code statements, so how could a bug have eluded such vigi-is tricky and lance? The answer requires, first, a closer look at software testing within thewhy testing is acontext of development. Second, it requires an understanding of the roleconstant trade-off.
V
ss
software testers and developers—two verydifferent functions—play.
Assuming that the bugs users reportoccur in a software product that really is inerror, the answer could be any of these:The user executed untested code. Becauseof time constraints, it’s not uncommon fordevelopers to release untested code—codein which users can stumble across bugs. The order in which statements were exe-cuted in actual use differed from that dur-ing testing.This order can determinewhether software works or fails.
The user applied a combination ofuntested input values. The possible inputcombinations that thousands of userscan make across a given software inter-face are simply too numerous for testersto apply them all. Testers must maketough decisions about which inputs to
s
test, and sometimes we make the wrongdecisions.
The user’s operating environment wasnever tested. We might have known aboutthe environment but had no time to testit. Perhaps we did not (or could not)replicate the user’s combination ofhardware, peripherals, operating sys-tem, and applications in our testing lab.For example, although companies thatwrite networking software are unlikelyto create a thousand-node network intheir testing lab, users can—and do—create such networks.
s
Through an overview of the softwaretesting problem and process, this articleinvestigates the problems that testers faceand identifies the technical issues that anysolution must address. I also survey existingclasses of solutions used in practice.
0740-7459/00/$10.00 © 2000 IEEE
70
IEEE SOFTWAREJanuary/February 2000
Qing Yi. Software Practice & Experience. John ...Tutorial On Using POET To Optimize and Tune ...Types of dependences; Testing for dependence; ...
and Testing in an Agile Environment What Do ...software – Frequently, after code is available ...Agile projects practice testing iteration, as well...
QuickTest Pro 8[1].2 Tutorial_计算机软件及...Testing Plan: Computer: QTP: What process and ...Close unneeded software (anti-virus, etc) ...
The tutorial is based on our recent text book on software product line ...requirements engineering and product line testing activities (see Fig. 1): ...
QuickTest Pro 8.2 Tutorial_演讲/主持_工作范文...Testing Plan: Computer: QTP: What process and ...Close unneeded software (anti-virus, etc) ...
SOEN 343Software DesignSOEN 343Software Design隐藏...v.size()); } } What is OO Analysis and ...[in] aName : String ) Practice in Tutorial ?...
A reduction in defects found during testing减少...There is tutorial work EVERY week ? There are ...? Software Engineering: Theory and Practice ? ...
Lecture Note 01 4 What is Software Engineering? ...? Software Testing: the process of checking the ...Research and practice in engineering safety-critical...
The different phases in the software development ...and the testing of g r a m m a r ...The workbench is designed as a tutorial system ...
Tutorial Slides Introduction 1 The causes of “We... through iterative design, analysis and testing. ...2003 11 John & Bass What is software ...
热门文档