This book will teach you how to test computer software under real-world conditions. The authors have all been test managers and software development managers at well-known Silicon Valley software companies. Successful consumer software companies have learned how to produce high-quality products under tight time and budget constraints. The book explains the testing side of that success.

Who this book is for:
* Testers and Test Managers
* Project Managers-Understand the timeline, depth of investigation, and quality of communication to hold testers accountable for.
* Programmers-Gain insight into the sources of errors in your code, understand what tests your work will have to pass, and why testers do the things they do.
* Students-Train for an entry-level position in software development.

What you will learn:
* How to find important bugs quickly
* How to describe software errors clearly
* How to create a testing plan with a minimum of paperwork
* How to design and use a bug-tracking system
* Where testing fits in the product development process
* How to test products that will be translated into other languages
* How to test for compatibility with devices, such as printers
* What laws apply to software quality

Average Customer Review: ( 47 customer reviews )
Write an online review and share your thoughts with other customers.

I have found Chapters 2, 3, 7, 11 and 12 to be the most useful and poignant to the average engineer. Not only is each chapter well laid out, but the authors also offer compelling arguments in each chapter to back up their arguments as well. I enjoyed particularly Chapter 3 the section on Path Testing, which conjures up horror stories from my development days. In this section the authors assert that 100% path testing does not imply 100% test coverage. They go on to argue with some rigor why the two are not necessarily the same. Many of you as I can probably claim that though all of the paths in their code were tested, verification was still able to find some condition that would make some part of the code fail. This chapter explains why this may be so and methodologies on how to attack testing those areas.

You will find the book well structured, informative and actually intuitive to navigate through. Each chapter builds on the previous chapters to provide the engineer with a clear idea of all the steps and intricacies involved in testing and verifying complex programs. It can therefore be used by the beginner as a source book for specific test applications, or by the team lead or manager who needs to know more about the actual scope and planning of a complex testing project. This book surely fills a great void in the area of publications software verification.

33 of 35 found the following review helpful:

If you read only one book on software testing, read thisAug 13, 2001
By Bret Pettichord
This book should sit on the desk of every software tester.

Many books will tell you how to test when you have enough time and cooperation. This book tells you what to do when the schedule is tight, the specification is missing, and the developers are tired of your focus on problems. It has sound advice and is a pleasure to read. I keep coming back to it. Feel like you have an impossible job? Read this book.

(Note: this book was published in 1993 and has not been updated since then. Wiley lists 1999 as the publication date because that was when they became the new publisher for the book, which is destined to become a classic.)

22 of 22 found the following review helpful:

Excellent orientation for new test professionalsJul 08, 2004
By Mike Tarrani "Jazz Drummer"
When I first read this book over eight years ago I was less than enthusiastic. At the time I felt that the approach was not rigorous enough. Over time I came to appreciate the pragmatism and how the approach in this book reflects the realities of software testing instead of a rigid, purist view as an unattainable ideal.

Everything the new or intermediate test professional needs to know is covered. The practices and techniques provided will foster sound QA practices and will step you through developing test strategies, and from those, developing and executing test cases. These are the real essence of testing, and this book covers them exceptionally well.

I like the coverage of testing systems and artifacts that are not software - documentation, hardware, and localization testing advice shows that testing is not limited to software. As importantly, the chapter on legal consequences of software defects will show testing in a perspective that is often overlooked, even by seasoned test professionals.

If you are new to software testing, or have some experience, but no formal training, this book will provide you with the right way to approach software testing, and will give insights that would take years to learn on your own.

29 of 31 found the following review helpful:

Single best book on practical software testingOct 30, 1999
By Howard Fear
One great testing book. What makes it great? It is pragmatic from start to finish. It addresses real problems in the world of software testing. And does so acknowledging that there's never enough time to do everything you want let alone trying to fulfill the overblown government perscriptions of ISO, SEI, and CMM.

19 of 19 found the following review helpful:

Excellent, informative book. Covers most test topics.Jan 28, 1999
By Wendy Cartmill (wendyc@prolynx.com)
This book provides an comprehensive guide to software testing. It covers all aspects of testing - e.g., test types, methods, plans, scripts, and cases. An excellent training and reference tool. It is useful to managers and experienced testers, and would be an excellent training tool for novice testers.

See all 47 customer reviews on Amazon.com