- Paperback: 320 pages
- Publisher: Wiley; 1 edition (December 31, 2001)
- Language: English
- ISBN-10: 0471081124
- ISBN-13: 978-0471081128
- Product Dimensions: 7.2 x 0.6 x 8.9 inches
- Shipping Weight: 1.3 pounds (View shipping rates and policies)
- Average Customer Review: 4.5 out of 5 stars See all reviews (70 customer reviews)
- Amazon Best Sellers Rank: #272,825 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Lessons Learned in Software Testing: A Context-Driven Approach 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2017 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
"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)
"...part of a rare breed of informative books which are both accessible to beginners whilst still being of great use to experts. No matter how much you know about software testing, Kaner, Bach and Pettiford still have a few lessons to teach you..." (M2 Communications, 7 June 2002)
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top customer reviews
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!