Posted by cadsmith on October 24, 2007
Reviewed Software Testing Techniques: Finding the Defects that Matter, Loveland and others, 2005. Finding the software defects that disrupt enterprise computing environments is the goal of the tester. Not all bugs will be found, so effort is directed to making the testing count. The development models covered include waterfall, waterwheel, common element, agile, spiral, evolutionary, test-driven, reactionary and iterative. There is a chapter on how teams can be used to test complex software. The various sources of information to seek when one is getting up to speed on the system design and operation are presented. Testplan contents are outlined. Test tools that can be bought or built are looked at. Common errors that might be found include specifications, data corruption, recoverability, and customer workloads. This also talks about simulators and virtual computers. Useful bug fixing metrics are listed, the highest priority measure being what impacts customers adversely. Scheduling tradeoffs are explored. IEEE standard 829-1998 defines software test documentation. The case studies in each chapter talk about realworld experiences which are useful to understand the issues that may not be obvious from merely an abstract test technique. A brief description of a web self-service corporate pension plan system is included.
This book discusses testing of software that is built to run on computers and clusters. Some networking terms are briefly discussed, but other sources would be useful if this is the focus. Similarly for embedded devices. Test equipment vendors might also provide additional information to fill in particular details of this comprehensive text. Actual software components might also add techniques, e.g. operating system toolset. Tests customized for specific hardware would need additional sources. Underlying hardware defects are out of the scope of this book. New technologies invite innovative software approaches and may also thus require testing advances.