
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera, scan the code below and download the Kindle app.
Follow the authors
OK
How to Break Software: A Practical Guide to Testing Paperback – 21 June 2002
Save Extra with 4 offers
7 days Replacement
Replacement Reason | Replacement Period | Replacement Policy |
---|---|---|
Physical Damage, Defective, Wrong and Missing Item | 7 days from delivery | Replacement |
Replacement Instructions

Read full returns policy
Purchase options and add-ons
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.
- ISBN-100201796198
- ISBN-13978-0201796193
- Edition1st
- PublisherPearson
- Publication date21 June 2002
- LanguageEnglish
- Dimensions17.53 x 1.78 x 22.86 cm
- Print length208 pages
Frequently bought together

Product description
From the Back Cover
* 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.
About the Author
James A. Whittaker is a well-known speaker and consultant, as well as seasoned professor.
Product details
- Publisher : Pearson; 1st edition (21 June 2002)
- Language : English
- Paperback : 208 pages
- ISBN-10 : 0201796198
- ISBN-13 : 978-0201796193
- Dimensions : 17.53 x 1.78 x 22.86 cm
- Best Sellers Rank: #793,088 in Books (See Top 100 in Books)
- #433 in Software Testing
- #1,848 in Software Design & Engineering
- #1,896 in Introductory & Beginning Programming
- Customer Reviews:
About the authors
Discover more of the author’s books, see similar authors, read book recommendations and more.
James Whittaker is a speaker, author, futurist and distinguished engineer who specializes in creativity and stagecraft.
Customer reviews
Top reviews from India
Top reviews from other countries
-
BjörnKReviewed in Germany on 8 May 2013
1.0 out of 5 stars Nichts neues
Verified PurchaseDie in dem Buch beschriebenen Vorgehensweisen beim Testen von Software sind jedem Tester mit gesundem Menschenverstand bekannt. Die Hinweise zu Testdaten und Testvorgehen dürften im Standard-Repertoire jeder modernen Testsuite bereits enthalten sein.
- LalaReviewed in the United States on 23 September 2008
5.0 out of 5 stars most thorough and organized book for beginners
Verified PurchaseThsi book was recommended by two people working at Microsoft. One was a Test Lead in IIS team and another a Test Manager with the Games for Windows team. I thought that being the case it would be worth giving it a shot. Here are some of my observations:
1) This book is fast paced.
2) Every point is made succinctly and not blabbered on, so it keeps your interest througout.
3) Provides lots of examples to help relate. Many are errors in MS Word 2000, which also makes it interesting to read.
4) Covered many distinct types of approaches, so is very thorough and organized. Different types of testing, types of attack within each type of testing, how/what/when details of the attack is all listed. Nothing left out.
5) Aimed towards newbies to testing, but is a good quick refresher resource for those who have been into testing for a little bit.