- Create your FREE Amazon Business account to save up to 10% with Business-only prices and free shipping.
Lessons Learned in Software Testing: A Context-Driven Approach 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
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
Frequently bought together
Special offers and product promotions
"...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)
- ASIN : 0471081124
- Publisher : Wiley; 1st edition (December 31, 2001)
- Language : English
- Paperback : 320 pages
- ISBN-10 : 9780471081128
- ISBN-13 : 978-0471081128
- Item Weight : 1.19 pounds
- Dimensions : 7.2 x 0.9 x 9 inches
- Best Sellers Rank: #211,255 in Books (See Top 100 in Books)
- Customer Reviews:
About the authors
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Lessons Learned is a terrific compilation of 293 "lessons" - short, real-world, easily-readable treatments of a range of topics relevant to new and seasoned testers, developers, managers, and executives. These lessons, culled from the experiences of the authors, are arranged in chapters addressing everyday topics you might face:
- The Role of the Tester
- Thinking Like a Tester
- Testing Techniques
- Bug Advocacy
- Automating Testing
- Documenting Testing
- Interacting with Programmers
- Managing the Testing Project
- Managing the Testing Group
- Your Career in Software Testing
- Planning the Testing Strategy
Of all the testing books I have on my bookshelf, this is the one I find myself coming back to time after time.
I've even gone as far as purchasing a copy of this book for each member of my Test Team, and using it in group discussions. We find ourselves disagreeing about some of the points made in the book (as you will too), but we have found that virtually all of the lessons lead to a lively discussion about software, testing, and our profession. Books that are this thought-provoking are rare.
I'm convinced that every software tester who reads this book will find at least a few gems that are particularly relevant for their individual situation. And I believe that most folks will find most of the book extremely valuable.
The book is organized around 293 lessons which are a paragraph to a couple pages long. The lessons are organized around eleven chapters. At first, I was annoyed by the structure of the book, but as I got used to it, I started to appreciate the structure in different lessons. Especially since it helped the authors in expressing conflicting thoughts well.
The first chapters cover the most basic questions. The first is about the role a tester has and already here the authors present a perhaps controversial view on testing as a service as opposed to as a quality police, which is often seen in larger organizations. The second chapter relates to how to think as a tester. It provides interesting references in completely different knowledge areas which might help testers become better. The third chapter is somewhat misplaced in the book, though still useful. It's a chapter that covers different testing techniques. It doesn't cover it thoroughly, but that is not the purpose of this book. For more thorough coverage of testing techniques, its probably better to pick up another book.
The fourth chapter is about writing bugs. Its insightful since it especially clarifies a lot about the role of testing from the authors perspective. The fifth chapter covers test automation and makes important observations related to test automation... especially that test automation is not the same as automated manual testing. I found the wording insightful and again stresses the role of the tester and especially the skill of testers.
Chapter six is perhaps one of the more controversial ones about documenting testing. As a logical conclusion from the focus on the role of tester (mentioned earlier), it makes sense to limit the documentation somewhat. Documentation is not a substitute for skill. However, they provide a balanced view and do not recommend to throw your documentation out of the window, but instead analyze your particular situation and create only the documentation that is needed.
The next three chapters relate to working with other persons. First how to work with programmers, then how to manage a testing project and how to manage a testing group. Chapter ten relates to building a testing career. Also here, some of the advise is general to "a career", not specifically a testing one.
The last chapter about strategy seemed to me somewhat odd. The book would have ended well with the manage your testing career and its not totally clear to me why the authors added this chapter still. It's not useless, just doesn't seem to fit in very well.
All in all, the book is a good read! It's funny and very insightful and sometimes controversial. I was considering a rating of four or five stars. I was thinking about four since I did not always agree with the authors for example, on their views on test automation. Though, lots has been learned about that the last years! On the other hand, I do not know any more insightful book related to this subject. And, I'd even recommend it to people who do not do software testing at all! So, therefore I decided to go for five stars! Well worth reading!
Top reviews from other countries
But it also covers some less obvious issues such as thinking like a tester, bug advocacy, and how to interact with programmers. The style is to offer the advice in bite sized chunks, and, to my surprise, it works, making it easy to look up something only half remembered, in a moment.
Even more importantly, from my point of view, the book is easily useable if you aren't a professional tester. If you are a programmer, or even the CTO, in a small company that doesn't have a software testing department, you will still get a lot of new ideas out of the book. Many of the ideas are a nice fit with programmer test driven development - some of them will work for you, some won't. Happily, the book isn't dogmatic, it's much more of a 'this is what we have found can work in some of the projects we have been involved in' style. And it works very well indeed.
This is the best software testing book I ever read. Sharing valuable experience and content are really helpful.