How to Break Software: A Practical Guide to Testing / Edition 1

Paperback (Print)
Buy Used
Buy Used from BN.com
$27.29
(Save 41%)
Item is in good condition but packaging may have signs of shelf wear/aging or torn packaging.
Condition: Used – Good details
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 95%)
Other sellers (Paperback)
  • All (25) from $1.99   
  • New (10) from $22.99   
  • Used (15) from $1.99   

Overview

How to Break Software is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. The testing techniques in this book are as flexible as conventional testing is rigid. And flexibility is needed in software projects in which requirements can change, bugs can become features and schedule pressures often force plans to be reassessed. Software testing is not such an exact science that one can determine what to test in advance and then execute the plan and be done with it. Instead of a plan, intelligence, insight, experience and a "nose for where the bugs are hiding" should guide testers. This book helps testers develop this insight. The techniques presented in this book not only allow testers to go off-script, they encourage them to do so. Don't blindly follow a document that may be out of date and that was written before the product was even testable. Instead, use your head! Open your eyes! Think a little, test a little and then think a little more. This book does teach planning, but in an "on- the-fly while you are testing" way. It also encourages automation with many repetitive and complex tasks that require good tools (one such tool is shipped with this book on the companion CD). However, tools are never used as a replacement for intelligence. Testers do the thinking and use tools to collect data and help them explore applications more efficiently and effectively.

Read More Show Less

Product Details

  • ISBN-13: 9780201796193
  • Publisher: Addison-Wesley
  • Publication date: 5/1/2002
  • Edition description: Book & CD-ROM
  • Edition number: 1
  • Pages: 178
  • Sales rank: 932,246
  • Product dimensions: 7.00 (w) x 9.00 (h) x 0.50 (d)

Meet the Author

James A. Whittaker is a well-known speaker and consultant, as well as seasoned professor.

Read More Show Less

Table of Contents

Preface.

Dedication.

Chapter Summaries.

I. INTRODUCTION.

1. A Fault Model to Guide Software Testing.

The Purpose of Software Testing.

Understanding Software Behavior.

Understanding Software's Environment.

The Human User.

File System User.

The Operating System User.

The Software User.

Understanding Software's Capabilities.

Testing Input.

Testing Output.

Testing Data.

Testing Competition.

Summary and Conclusion.

Exercises.

References.

II. USER INTERFACE ATTACKS.

2. Testing from the User Interface: Inputs and Outputs.

Using the Fault Model to Guide Testing.

Exploring the Input Domain.

First Attack: Apply inputs that force all the error messages to occur.

Second Attack: Apply inputs that force the software to establish default values.

Third Attack: Explore allowable character sets and data types.

Fourth Attack: Overflow input buffers.

Fifth Attack: Find inputs that may interact and test various combinations of their values.

Sixth Attack: Repeat the same input or series of inputs numerous times.

Exploring Outputs.

Seventh Attack: Force different outputs to be generated for each input.

Eighth Attack: Force invalid outputs to be generated.

Ninth Attack: Force properties of an output to change.

Tenth Attack: Force the screen to refresh.

Conclusion.

Exercises.

References.

3. Testing from the User Interface: Data and Computation.

Testing Inside the Box.

Exploring Stored Data.

Eleventh Attack: Apply inputs using a variety of initial conditions.

Twelfth Attack: Force a data structure to store too many/too few values.

Thirteenth Attack: Investigate alternate ways to modify internal data constraints.

Exploring Computation and Feature Interaction.

Fifteenth Attack: Force a function to call itself recursively.

Sixteenth Attack: Force computation results to be too large or too small.

Seventeenth Attack: Find features that share data or interact poorly.

Conclusion.

Exercises.

III. SYSTEM INTERFACE ATTACKS.

4. Testing from the File System Interface.

Attacking Software from the File System Interface.

Media-based Attacks.

First Attack: Inject faults that simulate memory access problems.

Second Attack: Inject faults that simulate network problems.

Third Attack: Damage the media.

File-based Attacks.

Fourth Attack: Assign an invalid file name.

Fifth Attack: Vary file access permissions.

Sixth Attack: Vary/corrupt file contents.

Exercises.

5. Testing from the Software/OS Interface.

Attacking Software from Software Interfaces.

Record-and-Simulate Attacks.

Observe-and-Fail Attacks.

Conclusion.

Exercises.

IV. CONCLUSION.

6. Some Parting Advice.

You'll Never Know Everything.

Bug Hunts.

Friday Afternoon Bug Fests.

Conclusion.

References.

APPENDICES.

Annotated Glossary of Programming Terms.

Appendix A. Testing Exception and Error Cases Using Runtime Fault Injection.

Introduction.

A Mechanism for Runtime Fault Injection.

Fault Selection.

Conclusions.

Acknowledgments.

References.

Appendix B. Using HEAT: The Hostile Environment Application Tester.

Canned HEAT User Guide.

The Application Band.

The Monitor Band.

Fault Injection Bands and Their Functionality.

The Network Band.

Disk Storage.

Memory.

Appendix C. What is Software Testing? And Why is it so Hard?

Introduction.

The Software Testing Process.

Phase One: Modeling the Software's Environment.

Phase Two: Selecting Test Scenarios.

Phase Three: Running and Evaluating Test Scenarios.

Phase Four: Measuring Testing Progress.

Conclusion.

References.

The Software Testing Problem.

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
Sort by: Showing all of 3 Customer Reviews
  • Anonymous

    Posted October 29, 2003

    How many times can we plug our own testing app

    I¿m very disappointed in reading this book, the first two chapters give valuable information, however the remainder of the chapters is a constant plug for `Canned Heat¿, the application the writers students developed. A checklist for battle is a good description of what to think about while testing, but is common knowledge for seasoned testers.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted November 17, 2009

    No text was provided for this review.

  • Anonymous

    Posted October 24, 2008

    No text was provided for this review.

Sort by: Showing all of 3 Customer Reviews

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