A tester’s mind is never at rest. It is constantly searching, over populated with information, and continually discovering changes to context. A tester at work is interacting with plenty of people who don’t understand testing, pretend to understand or have conflicting ideas of testing. A combination of all this creates restlessness in a tester’s mind. A restless mind ends up with fragmented learning and chaos. This impacts the quality of life itself. Is this book for you?
I stumbled on this book for little more reason than I'm a tester (now a longstanding Head of QA at a market leading London software house) with a love for spiritual wisdom and insights.
This book is somewhat short on the latter but never in my life in testing have I found a clearer or more concise definition of what good testing looks like, across the job role and throughout the organisation. This is the kind of Testing culture those of us rushing after best practice hope to build.
To Pradeep - I congratulate you on thoroughly understanding our discipline and sharing that wisdom as widely as you have.
I bought this book because of good reviews on Goodreads, but I have mixed feelings about it. The book is very short, which can be good, but the content could easily be a blog post. About 20% of the book explains why it was written and includes thank-you lists. Many pages have only one sentence. This might be a way to present ideas, but it feels like too much.
The author talks about chaos in different-sized organizations. He suggests finding inner peace instead of fighting it. While this can be helpful, it might lead to accepting bad quality practices.
I agree with the author that many companies focus too much on automation tests to improve quality. Instead, they should try to fix problems with company culture.
The author often mentions his LinkedIn posts that reached many developers. While this might show his experience, it doesn't feel right for a good book.
I expected more from a recent book, hoping to find solutions to modern problems. It wasn't a waste of time to read, but I would suggest borrowing it instead of buying. For those looking to spend money on a testing book, I recommend "Lessons Learned in Software Testing." You can go back to that book many times and learn more.
In summary, "Buddha in Testing" has some good points but falls short in several areas. It might be worth a quick read, but there are better options for those seeking in-depth knowledge about software testing.
A book I bought when I started my career as a QA, at first I understood little about the problems the book described but as my career gained experience it made more and more sense. That's why I always started the book again, taking into account that this is a book that you finish in one or two days, I taked several years to finish.
It is a book that anyone involved in the QA process should read at some point. It will help a lot to identify communication problems and manage expectations with the different roles that interact in software development, which is in part what a QA does all the time.
---
Un libro que compre cuando inicie mi carrera como QA al principio entendía poco sobre los problemas que describía el libro pero a medida que mi carrera iba tomando experiencia tenía más y más sentido. Por eso siempre comenzaba el libro de nuevo , tendiendo en cuenta que este es un libro que terminas en un o dos días , yo dure con el varios años.
Es un libro que cualquier persona ligada al proceso de QA debería de leer en algún momento ayudará mucho a identificar problemas de comunicación y manejar expectativas con los diferentes roles que interactúan en el desarrollo de software, que en parte es lo que hace un QA todos los días.
This book delve into testing very vividly and clearly articulated things bothered Testers as well as thoughts that cloud thinking of Testers. Truly a light house kind of work, in that guides Testers greener pastures of delivering value to business.
Had this book been available twelve years ago, that would have given my whole testing team a copy and a session from Pradeep.
Highly recommend this book for anyone in Product Development, software development and maintenance, it doesn't matter which role.. To develop and set right expectations for testing.
Great book for finding the peace within you as a tester
This book highlights the feelings and thoughts from tester no the real testers. Shifting Quality from testing to overall organization and everyone has take the responsibility of the quality of the product not only tester. Great writing Pradeep,keep writing on testing
I want every tester to read this one. This can be a perfect 5 star but I still want to learn more from pradeep soundarajan and he might have added more stories which he has already spoken in conferences He is an inspiration for me ever since I started testing. This book was just like him telling the stories about testing. I loved it. Just read it and be proud to be a software tester.
I did enjoy this book: - It was short and manageable - It lent itself to reading one or two pages, then some reflection - The author has some really good industry experience
Unfortunately this book suffered in quality. Often it's unclear what the author means, and reads like unedited notes.
A book full of questions to be asked to the inner self. Eye-opening book, a different perception and an important one too. Would recommend developers, testers and business analysis people to read this, as it will help them grow with peace. ❤️
Maybe my mindset was not the right one when I read it. There are a couple of ideas I walk away with. So, thanks for that. I think reading this is not a waste of time. I do invite anyone to read it.
Very nicely written. Crisp summary and a sagacious thought. Would have been helpful to have a companion book that is technical and detailed for those interested to know more.