Lessons Learned in Software Testing: A Context-Driven Approach

Book Description

Decades of software testing experience condensed into the most important lessons learned.

The world's leading software testing experts lend you their wisdom and years of experience to help you avoid the most common mistakes in testing software. Each lesson is an assertion related to software testing, followed by an explanation or example that shows you the how, when, and why of the testing lesson. More than just tips, tricks, and pitfalls to avoid, Lessons Learned in Software Testing speeds you through the critical testing phase of the software development project without the extensive trial and error it normally takes to do so. The ultimate resource for software testers and developers at every level of expertise, this guidebook features:

• Over 200 lessons gleaned from over 30 years of combined testing experience
• Tips, tricks, and common pitfalls to avoid by simply reading the book rather than finding out the hard way
• Lessons for all key topic areas, including test design, test management, testing strategies, and bug reporting
• Explanations and examples of each testing trouble spot help illustrate each lesson's assertion

Book Reviews

"If testing is something that is going to be an important part of your career buy this book and read it carefully." (CVu - Jnl of the Association C & C++ Users, February 2002)

"...a real gem?for me, this book is one that I shall find useful?each and every test department should have several copies available...be prepared to be inspired, or at the very least to have your ideas challenged..." (Professional Tester, September 2002)

"...a refreshing and enjoyable book?it will not be 'shelf-ware', but a well-used reference..." (Software Testing, Verification & Reliability, March 2003)

"...will make fascinating reading?highly recommended..." (CVu, Dec 03)

About the Author

CEM KANER, JD, PhD, is a professor of computer sciences at Florida Institute of Technology. He also consults on technical and management issues, and practices law within the software development community. He is the lead author of two books, Testing Computer Software and Bad Software (both from Wiley).

JAMES BACH is founder and principal consultant of Satisfice, Inc., a software testing and quality assurance company. His experience with competitive software development in leading Silicon Valley companies, such as Apple and Borland, led him to specialize in such aspects of the craft as "good enough" quality, risk-based testing, exploratory testing, and other techniques that require skill and judgment. He has also served as Chief Scientist at Software Testing Labs.

BRET PETTICHORD works as an independent consultant and edits the popular Software Testing Hotlist at www.testinghotlist.com. A frequent speaker and writer, he is also the founder of the Austin Workshop on Test Automation.

Customer Reviews

"Lessons Learned in Software Testing" is a great book for the experienced tester or test manager. The book is structured as a series of bite-sized lessons, with a few longer essays on the authors' favorite test techniques thrown in. In the lessons, the authors share their opinions (frankly presented as such), and then explain the reasoning behind those opinions. They concentrate on explaining how to apply the same sort of reasoning to your own situation. In a few spots, the authors actually present contradicting opinions and proceed to defend both.

The lessons cover a wide range of subjects vital to testing and test management - everything from test planning to career guidance to the role of the test group in the organization. I found lessons that presented new (and promising) ways to think about my current knotty problems, and a few that made me question practices that I'd considered tried-and-true for years. If you're faced with problems that are puzzling, hard to describe, vague and inchoate, there's probably a lesson in this book that will bring the problem into focus for you. You may walk away with more questions than answers, but they'll be good, crisp, probing questions.

I consider this book a "must-have" for anyone who's been in testing long enough to realize that the books aren't always right.

This book is not a tutorial on "how to test." While it offers some suggestions, its aim is to pass on to the reader some significant considerations learned over the years by the authors.

While it does cover some rules of thumb for testing techniques, it goes further. It provides insight into the human element of testing and gives practical advice on how to communicate defects, trust in the doers to make estimates, understand the importance of a diverse culture and other areas that have a significant impact on the development process. This is all done well within the context of the impact to software testing.

If you're a development manager, I strongly recommend this book.