Software Testing

Topics: Software testing, Software engineering, System software Pages: 19 (6211 words) Published: June 29, 2010
Software Testing
Carnegie Mellon University
18-849b Dependable Embedded Systems
Spring 1999
Authors: Jiantao Pan

Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. [Hetzel88] Although crucial to software quality and widely deployed by programmers and testers, software testing still remains an art, due to limited understanding of the principles of software. The difficulty in software testing stems from the complexity of software: we can not completely test a program with moderate complexity. Testing is more than just debugging. The purpose of testing can be quality assurance, verification and validation, or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing. Software testing is a trade-off between budget, time and quality.

* Introduction
* Key Concepts
* Taxonomy
* Testing automation
* When to stop testing?
* Alternatives to testing
* Available tools, techniques, and metrics
* Relationship to other topics
* Conclusions
* Annotated Reference List & Further Reading

Software Testing is the process of executing a program or system with the intent of finding errors. [Myers79] Or, it involves any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. [Hetzel88] Software is not unlike other physical processes where inputs are received and outputs are produced. Where software differs is in the manner in which it fails. Most physical systems fail in a fixed (and reasonably small) set of ways. By contrast, software can fail in many bizarre ways. Detecting all of the different failure modes for software is generally infeasible. [Rstcorp] Unlike most physical systems, most of the defects in software are design errors, not manufacturing defects. Software does not suffer from corrosion, wear-and-tear -- generally it will not change until upgrades, or until obsolescence. So once the software is shipped, the design defects -- or bugs -- will be buried in and remain latent until activation. Software bugs will almost always exist in any software module with moderate size: not because programmers are careless or irresponsible, but because the complexity of software is generally intractable -- and humans have only limited ability to manage complexity. It is also true that for any complex systems, design defects can never be completely ruled out. Discovering the design defects in software, is equally difficult, for the same reason of complexity. Because software and any digital systems are not continuous, testing boundary values are not sufficient to guarantee correctness. All the possible values need to be tested and verified, but complete testing is infeasible. Exhaustively testing a simple program to add only two integer inputs of 32-bits (yielding 2^64 distinct test cases) would take hundreds of years, even if tests were performed at a rate of thousands per second. Obviously, for a realistic software module, the complexity can be far beyond the example mentioned here. If inputs from the real world are involved, the problem will get worse, because timing and unpredictable environmental effects and human interactions are all possible input parameters under consideration. A further complication has to do with the dynamic nature of programs. If a failure occurs during preliminary testing and the code is changed, the software may now work for a test case that it didn't work for previously. But its behavior on pre-error test cases that it passed before can no longer be guaranteed. To account for this possibility, testing should be restarted. The expense of doing this is often prohibitive. [Rstcorp] An interesting analogy parallels the difficulty...

References: * [Basili85] Victor R. Basili, Richard W. Selby, Jr. "Comparing the Effectiveness of Software Testing Strategies",
Technical Report, Department of Computer Science, University of Maryland, College Park, 1985
* [Beizer90] Boris Beizer, Software Testing Techniques. Second edition. 1990
* A very comprehensive book on the testing techniques
In-depth discussion about functional testing throughout all product life-cycle.
* [IEEE90] IEEE Standard Glossary of Software Engineering Terminology (IEEE Std 610.12-1990), IEEE Computer Soc., Dec
* Introduction of the tools BoundsChecker by NuMega
* [Parrington89] Norman Parrington and Marc Roper, Understanding Software Testing, Published by John Willey & Sons, 1989
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Localisation Testing Essay
  • Testing Heuristics Cheat Sheet Essay
  • Steps to Testing Web Applications Essay
  • Review of Paper
  • Essay about software testing
  • Essay on software testing
  • Software quality assurance and testing Essay
  • Btec Higher National Diploma in Software Development Assignment Specification Essay

Become a StudyMode Member

Sign Up - It's Free