The Art of Software Testing / Edition 2

Hardcover (Print)
Buy New
Buy New from
Used and New from Other Sellers
Used and New from Other Sellers
from $18.93
Usually ships in 1-2 business days
(Save 88%)
Other sellers (Hardcover)
  • All (4) from $18.93   
  • New (1) from $200.00   
  • Used (3) from $18.93   


Practical, up-to-date tactics and techniques for successful, efficient testing:
  • Basic testing principles and strategies
  • Program inspections and walkthroughs
  • Code inspections
  • Error checklists
  • Peer ratings
  • Black- and white-box testing
  • Error guessing
  • Top-down vs. bottom-up testing
  • Higher-order testing
  • Function and system testing
  • Acceptance testing
  • Installation testing
  • Module (unit) testing
  • Test planning and control
  • Independent testing agencies
  • Debugging principles
  • Error analysis
  • Extreme Testing
  • Testing Internet applications
  • Higher-order testing of e-commerce architectures
Read More Show Less

Editorial Reviews

This theoretical discussion of the purpose and nature of software testing emphasizes methodologies for the design of effective test cases. It comprehensively covers psychological and economic principles, managerial aspects of testing, test tools, high-order testing, code inspections, and debugging. Annotation c. Book News, Inc., Portland, OR
Read More Show Less

Product Details

  • ISBN-13: 9780471469124
  • Publisher: Wiley, John & Sons, Incorporated
  • Publication date: 6/21/2004
  • Series: Business Data Processing: A Wiley Series , #28
  • Edition description: REV
  • Edition number: 2
  • Pages: 256
  • Sales rank: 1,496,007
  • Product dimensions: 6.00 (w) x 9.00 (h) x 0.75 (d)

Meet the Author

GLENFORD J. MYERS is currently Director of Spectrum Signals. He is a former senior staff member of IBM’s Systems Research Institute, as well as the former CEO and founder of RadiSys Corporation.

TOM BADGETT is Chief Information Officer for IdleAire Technologies Corporation and manages a team of software developers who design and maintain sophisticated, real-time billing and customer support systems for this national firm. He has published more than fifty books on software and hardware and has served as technical editor for PCjr Magazine and Digital News. He has written hundreds of articles for major computer-oriented magazines.

TODD M. THOMAS is a professional software developer and database administrator with over nine years of experience. His career has exposed him to all sizes of software projects for both the private and government sectors. He has also authored Java Data Access, a book on how to use Java technology to leverage enterprise data stores.

COREY SANDLER is President of Word Association, a developer of computer, science, business, and travel books for many of the country’s largest publishing companies. He is the author of the bestseller Fix Your Own PC, and a former editorial director and editor in chief of Digital News. He has also served as New York bureau chief for PC Week and first executive editor of PC Magazine.

Read More Show Less

Read an Excerpt

The Art of Software Testing

By Glenford J. Myers Corey Sandler Tom Badgett Todd M. Thomas

John Wiley & Sons

ISBN: 0-471-46912-2

Chapter One

A Self-Assessment Test

Since this book was first published 25 years ago, software testing has become both easier and more difficult than ever.

Software testing is more difficult because of the vast array of programming languages, operating systems, and hardware platforms that have evolved. And, while relatively few people used computers in the 1970s, today virtually anyone in business or education could hardly complete a day's work without using a computer. Furthermore, the machines themselves are hundreds of times more powerful than those early devices.

Therefore, the software we write today potentially touches millions of people, enabling them to do their jobs effectively and efficiently-or causing them untold frustration and the cost of lost work or lost business. This is not to say that software is more important today than it was when the first edition of this book was published, but it is safe to say that computers-and the software that drives them-certainly affect more people and more businesses today.

Software testing is easier, in some ways, because the array of software and operating systems is much more sophisticated than ever, providing intrinsic well-tested routines that can be incorporated into applications without the need for a programmer to develop them from scratch. Graphical user interfaces (GUIs), forexample, can be built from a development language's libraries, and, since they are preprogrammed objects that have been debugged and tested previously, the need for testing them as part of a custom application is much reduced.

Software testing is a process, or a series of processes, designed to make sure computer code does what it was designed to do and that it does not do anything unintended. Software should be predictable and consistent, offering no surprises to users. In this book we will look at many approaches to achieving this goal.

Now, before we start the book, we'd like you to take a short exam.

We want you to write a set of test cases-specific sets of data-to properly test a relatively simple program. Create a set of test data for the program-data the program must handle correctly to be considered a successful program. Here's a description of the program:

The program reads three integer values from an input dialog. The three values represent the lengths of the sides of a triangle. The program displays a message that states whether the triangle is scalene, isosceles, or equilateral.

Remember that a scalene triangle is one where no two sides are equal, whereas an isosceles triangle has two equal sides, and an equilateral triangle has three sides of equal length. Moreover, the angles opposite the equal sides in an isosceles triangle also are equal (it also follows that the sides opposite equal angles in a triangle are equal), and all angles in an equilateral triangle are equal.

Evaluate your set of test cases by using it to answer the following questions. Give yourself one point for each "yes" answer.

1. Do you have a test case that represents a valid scalene triangle? (Note that test cases such as 1,2,3 and 2,5,10 do not warrant a "yes" answer because there does not exist a triangle having these dimensions.)

2. Do you have a test case that represents a valid equilateral triangle?

3. Do you have a test case that represents a valid isosceles triangle? (Note that a test case representing 2,2,4 would not count because it is not a valid triangle.)

4. Do you have at least three test cases that represent valid isosceles triangles such that you have tried all three permutations of two equal sides (such as, 3,3,4; 3,4,3; and 4,3,3)?

5. Do you have a test case in which one side has a zero value?

6. Do you have a test case in which one side has a negative value?

7. Do you have a test case with three integers greater than zero such that the sum of two of the numbers is equal to the third? (That is, if the program said that 1,2,3 represents a scalene triangle, it would contain a bug.)

8. Do you have at least three test cases in category 7 such that you have tried all three permutations where the length of one side is equal to the sum of the lengths of the other two sides (for example, 1,2,3; 1,3,2; and 3,1,2)?

9. Do you have a test case with three integers greater than zero such that the sum of two of the numbers is less than the third (such as 1,2,4 or 12,15,30)?

10. Do you have at least three test cases in category 9 such that you have tried all three permutations (for example, 1,2,4; 1,4,2; and 4,1,2)?

11. Do you have a test case in which all sides are zero (0,0,0)? 12. Do you have at least one test case specifying noninteger values (such as 2.5,3.5,5.5)?

13. Do you have at least one test case specifying the wrong number of values (two rather than three integers, for example)?

14. For each test case did you specify the expected output from the program in addition to the input values?

Of course, a set of test cases that satisfies these conditions does not guarantee that all possible errors would be found, but since questions 1 through 13 represent errors that actually have occurred in different versions of this program, an adequate test of this program should expose at least these errors.

Now, before you become concerned about your own score, consider this: In our experience, highly qualified professional programmers score, on the average, only 7.8 out of a possible 14. If you've done better, congratulations; if not, we'll try to help.

The point of the exercise is to illustrate that the testing of even a trivial program such as this is not an easy task. And if this is true, consider the difficulty of testing a 100,000-statement air traffic control system, a compiler, or even a mundane payroll program. Testing also becomes more difficult with the object-oriented languages such as Java and C++. For example, your test cases for applications built with these languages must expose errors associated with object instantiation and memory management.

It might seem, from working with this example, that thoroughly testing a complex, real-world program would be impossible. Not so! Although the task can be daunting, adequate program testing is a very necessary-and achievable-part of software development, as you will learn in this book.


Excerpted from The Art of Software Testing by Glenford J. Myers Corey Sandler Tom Badgett Todd M. Thomas Excerpted by permission.
All rights reserved. No part of this excerpt may be reproduced or reprinted without permission in writing from the publisher.
Excerpts are provided by Dial-A-Book Inc. solely for the personal use of visitors to this web site.

Read More Show Less

Table of Contents

List of Figures and Tables.



Chapter 1: A Self-Assessment Test.

Chapter 2: The Psychology and Economics of Program Testing.

The Psychology of Testing.

The Economics of Testing.

Black-Box Testing.

White-Box Testing.

Software Testing Principles.


Chapter 3: Program Inspections, Walkthroughs, and Reviews.

Inspections and Walkthroughs.

Code Inspections.

An Error Checklist for Inspections.

Data Reference Errors.

Data-Declaration Errors.

Computation Errors.

Comparison Errors.

Control-Flow Errors.

Interface Errors.

Input/Output Errors.

Other Checks.


Desk Checking.

Peer Ratings.


Chapter 4: Test-Case Design.

White-Box Testing.

Logic-Coverage Testing.

Equivalence Partitioning.

An Example.

Boundary-Value Analysis.

Cause-Effect Graphing.

Error Guessing.

The Strategy.

Chapter 5: Module (Unit) Testing.

Test-Case Design.

Incremental Testing.

Top-down versus Bottom-up Testing.

Top-down Testing.

Bottom-up Testing.

A Comparison.

Performing the Test.

Chapter 6: Higher-Order Testing.

Function Testing.

System Testing.

Facility Testing.

Volume Testing.

Stress Testing.

Usability Testing.

Security Testing.

Performance Testing.

Storage Testing.

Configuration Testing.

Compatibility/Configuration/Conversion Testing.

Installability Testing.

Reliability Testing.

Recovery Testing.

Serviceability Testing.

Documentation Testing.

Procedure Testing.

Performing the System Test.

Acceptance Testing.

Installation Testing.

Test Planning and Control.

Test Completion Criteria.

The Independent Test Agency.

Chapter 7: Debugging.

Debugging by Brute Force.

Debugging by Induction.

Debugging by Deduction.

Debugging by Backtracking.

Debugging by Testing.

Debugging Principles.

Error-Locating Principles.

Error-Repairing Techniques.

Error Analysis.

Chapter 8: Extreme Testing.

Extreme Programming Basics.

Extreme Testing: The Concepts.

Extreme Unit Testing.

Acceptance Testing.

Extreme Testing Applied.

Test-Case Design.

Test Driver and Application.


Chapter 9: Testing Internet Applications.

Basic E-commerce Architecture.

Testing Challenges.

Testing Strategies.

Presentation Layer Testing.

Business Layer Testing.

Data Layer Testing.

Appendix A: Sample Extreme Testing Application.

Appendix B: Prime Numbers Less Than 1,000.



Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)