Picture 1 of 1
Gallery
Picture 1 of 1
Have one to sell?
How to Break Software: A Practical Guide to Testing W/CD by Whittaker
US $4.99
ApproximatelyS$ 6.41
Condition:
“Used book in good condition. Shows typical wear. Quick shipping. Satisfaction guaranteed!”
Good
A book that has been read but is in good condition. Very minimal damage to the cover including scuff marks, but no holes or tears. The dust jacket for hard covers may not be included. Binding has minimal wear. The majority of pages are undamaged with minimal creasing or tearing, minimal pencil underlining of text, no highlighting of text, no writing in margins. No missing pages.
Oops! Looks like we're having trouble connecting to our server.
Refresh your browser window to try again.
Shipping:
US $9.99 (approx S$ 12.84) USPS Media MailTM.
Located in: Multiple Locations, United States
Delivery:
Estimated between Tue, 12 Aug and Mon, 18 Aug to 91768
Returns:
30 days return. Buyer pays for return shipping. If you use an eBay shipping label, it will be deducted from your refund amount.
Coverage:
Read item description or contact seller for details. See all detailsSee all details on coverage
(Not eligible for eBay purchase protection programmes)
Seller assumes all responsibility for this listing.
eBay item number:157212510214
Item specifics
- Condition
- Good
- Seller Notes
- “Used book in good condition. Shows typical wear. Quick shipping. Satisfaction guaranteed!”
- Book Title
- How to Break Software: A Practical Guide to Testing W/CD
- Topic
- Business Technology
- Narrative Type
- Business Technology
- Genre
- N/A
- Intended Audience
- N/A
- ISBN
- 9780201796193
About this product
Product Identifiers
Publisher
Pearson Education
ISBN-10
0201796198
ISBN-13
9780201796193
eBay Product ID (ePID)
2256428
Product Key Features
Number of Pages
208 Pages
Language
English
Publication Name
How to Break Software : a Practical Guide to Testing
Subject
Software Development & Engineering / Quality Assurance & Testing, General
Publication Year
2002
Type
Textbook
Subject Area
Computers
Format
CD-ROM / Trade Paperback
Dimensions
Item Height
0.7 in
Item Weight
12 Oz
Item Length
9 in
Item Width
6.9 in
Additional Product Features
Intended Audience
College Audience
LCCN
2002-018693
Dewey Edition
21
Illustrated
Yes
Dewey Decimal
005.1/4
Table Of Content
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.
Synopsis
How to Break Software takes a very applied and non-rigid approach to teaching how to test software for common bugs. It 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. Instead of relying on a rigid plan, it should be intelligence, insight, experience and a "nose for where the bugs are hiding" that 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., 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., 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.
LC Classification Number
QA76.76.T48W48 2003
Item description from the seller
Seller feedback (90)
- y***8 (4)- Feedback left by buyer.Past monthVerified purchaseGreat condition
- l***l (1047)- Feedback left by buyer.Past monthVerified purchaseI highly recommend this company based on their professional experience and expertise!!!
- b***1 (778)- Feedback left by buyer.Past monthVerified purchaseGood condition.
Seller feedback (90)
- y***8 (4)- Feedback left by buyer.Past monthVerified purchaseGreat condition
- l***l (1047)- Feedback left by buyer.Past monthVerified purchaseI highly recommend this company based on their professional experience and expertise!!!
- b***1 (778)- Feedback left by buyer.Past monthVerified purchaseGood condition.