Lessons Learned in Software Testing: A Context-Driven Approach 1st Edition

"Lessons learned in software testing" provides 293 lessons the authors learned during their many years working as software testers, test managers and consultants. This book is perhaps one of the most insightful books on testing ever written. It covers a broad range of testing issues and most of the topics are relevant outside the world of testing. To give an example, the authors discussions related to documentation, standards or licensing are not limited to testing. They clearly explain their thinking behind their arguments and parts like these are useful reads for anyone!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!

I'm often asked to recommend a good book about software testing. Sometimes I'm even asked what I think is the best book about software testing. I usually hesitate to ever say "best", since I believe the best for me may not necessarily be the best for you. But if I had to pick just one book that I think would prove to be the most valuable across the widest range of readers, it would be Lessons Learned in Software Testing by Cem Kaner, James Bach, and Bret Pettichord.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 StrategyOf 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.

I am a professional software tester. I found this book to be very good, full of great advice.I followed their advice of reading a little bit at a time - every day I read the book for 10 minutes. I was able to finish the book in just under 2 months. Would recommend this method for reading this book, because it is quite long.The book changed my philosophy on testing. I was starting to get a bit bored at my job because I am asked to run the same set of tests over and over. Now, instead of looking at those tests as just a list of tests I have to run exactly the same each time, I look at each test as a jumping off point to explore the application in more depth and find more bugs.I think the thing that I loved the most about this book is how the authors are so interested in testing and different methodologies. They are kinda like the "cool" teacher you had in high school, they make testing seem interesting! (I mean, it is, but after a while in testing, if you are at the wrong company, it can seem less interesting). If you've gotten burnt out on testing, this book can give you your spark back!The only small criticism I have is that the way the sections were organized seemed a little odd. Oh well, definately not enough to give this book any less than 5 stars!