The Art of Software Testing

Overview

The classic guide to software testing, updated

Since the first edition of The Art of Software Testing, the hardware and software of computing have changed dramatically.Yet this book has stood the test of time. Whereas most bookson software testing target particular development techniques,languages, or testing methods, The Art of Software Testing,Third Edition provides a brief but powerful and comprehensive presentation of time-proven software ...

See more details below
Hardcover
$127.85
BN.com price
(Save 9%)$141.95 List Price
Other sellers (Hardcover)
  • All (15) from $47.41   
  • New (11) from $89.52   
  • Used (4) from $47.41   
The Art of Software Testing

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK
  • NOOK HD/HD+ Tablet
  • NOOK
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac
  • NOOK for Web

Want a NOOK? Explore Now

NOOK Book (eBook)
$80.99
BN.com price
(Save 42%)$141.95 List Price

Overview

The classic guide to software testing, updated

Since the first edition of The Art of Software Testing, the hardware and software of computing have changed dramatically.Yet this book has stood the test of time. Whereas most bookson software testing target particular development techniques,languages, or testing methods, The Art of Software Testing,Third Edition provides a brief but powerful and comprehensive presentation of time-proven software testing approaches.

The new Third Edition applies the original classic principles to today's hot topics, including:

  • Testing apps for iPhones, iPads, BlackBerry smartphones, Android phones and tablets, and other mobile devices
  • Collaborative (user) programming and testing
  • Testing for Internet applications, e-commerce, and agileprogramming environments

Students and IT managers alike will find The Art of SoftwareTesting, Third Edition an indispensible resource that pays for itself with the first bug you discover and fix.

Read More Show Less

Editorial Reviews

Booknews
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 booknews.com
Read More Show Less

Product Details

  • ISBN-13: 9781118031964
  • Publisher: Wiley
  • Publication date: 11/8/2011
  • Edition number: 3
  • Pages: 240
  • Sales rank: 829,359
  • Product dimensions: 6.20 (w) x 9.10 (h) x 1.00 (d)

Meet the Author

GLENFORD J. MYERS is a technology executive and a former senior staff member of IBM's Systems Research Institute, as well as the founder and former CEO of RadiSys Corporation.

TOM BADGETT has managed software development teams for large national corporations, has published more than sixty books in the computer hardware and software field, and served as technical editor for PCjr, Digital News, and other national computer magazines.

COREY SANDLER is one of the pioneers of computer journalism. He covered technology for Gannett Newspapers and the Associated Press and went on to become the first executive editor of PC Magazine. He also was the founding editor of Digital News, the newspaperfor DEC minicomputers. He has written more than 150 books on computers, business, and other topics.

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.

(Continues...)



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

Preface vii

Introduction ix

1 A Self-Assessment Test 1

2 The Psychology and Economics of Software Testing 5

3 Program Inspections, Walkthroughs, and Reviews 19

4 Test-Case Design 41

5 Module (Unit) Testing 85

6 Higher-Order Testing 113

7 Usability (User) Testing 143

8 Debugging 157

9 Testing in the Agile Environment 175

10 Testing Internet Applications 193

11 Mobile Application Testing 213

Appendix Sample Extreme Testing Application 227

Index 233

Read More Show Less

Customer Reviews

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

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com 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 & Noble.com 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 & Noble.com 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 BN.com 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

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com 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 BN.com. 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)