How to Break Software: A Practical Guide to Testing by James A. Whittaker

BUY IT NEW

  • $46.40 Online Price
    $41.76 Member price
    (Save 10%)
    Limited Time Offer! Everyone receives the Member Price on books.
    See Details
    • skip to cart
  • Add To List uiAction=GetAllLists&page=List&pageType=list&ean=9780201796193&productCode=BK&maxCount=100&threshold=3

GET FREE SHIPPING ON ORDERS OF $25 OR MORE

DELIVERY & GIFT DETAILS:

Usually ships within 24 hours

Delivery Time and Shipping Rates

Eligible for gift wrap & gift message.

BUY IT USED

9 copies from $13.00

See All Available

Pick Me Up

Reserve it at BN.com & pick it up in 60 minutes at your local store.

Enter a zip code

Textbook (Paperback - Book & CD-ROM)

  • 178pp
  • Sales Rank: 136,736

Reader Rating: (3 ratings)

Detailed Rating: "General Readers" See All

TEXTBOOK INFORMATION

  • ISBN-13: 9780201796193
  • Edition Description: Book & CD-ROM
  • Edition Number: 1
  • Pub. Date: May 2002
  • Publisher: Addison Wesley
Buy it Used: 9 copies from $13.00 See All Available

Customers who bought this also bought

 
  • Overview
  • Editorial Reviews
  • Customer Reviews
  • Features

Product Details

  • Pub. Date: May 2002
  • Publisher: Addison Wesley
  • Format: Textbook Paperback, 178pp
  • Sales Rank: 136,736

Synopsis

Practical tutorial on how to actually do testing by presenting numerous "attacks" you can perform to test your software for bugs.

  • Practical approach has little or no theory, but shows real ways effectively test software—accessible to beginners and seasoned testers.
  • The author is well known and respected as an industry consultant and speaker.
  • Uses market leading, and immediately identifiable, software applications as examples to show bugs and techniques.

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.

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

More Reviews and Recommendations

Biography

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

Customer Reviews

  • Reader Rating:
  • Ratings: 3Reviews: 1

How many times can we plug our own testing appby Anonymous

Reader Rating:
See Detailed Ratings

October 29, 2003: 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.