How to Break Software: A Practical Guide to Testing W/CD

Description

Features

Features

• Uses an applied, tutorial approach to teaching software testing.

• Demonstrates a method for testing software at the most common places that bugs appear: The User Interface, the File Systems Interface, and the Operating System Interface.

• Teaches planning in a methodical “on–the–fly while you are testing” way.

• Encourages automation with many repetitive and complex tasks that require good tools.

• Contains CD with HEAT: Hostile Environment Application Tester, software that provides a mechanism to easily trip exceptions and force error code to execute. HEAT can be used to simulate a faulty network, low memory, a full hard drive and any number of other common failure scenarios. Also includes Holodeck Lite.

• Written by a seasoned professor, trusted consultant, and standing–room–only speaker.

• Endorsed by the directors of testing at IBM, Rational Software Corporation, and Microsoft.

From the back cover:

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.

About the Author:

Author Bios

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