❓ Why you should read "Taking Testing Seriously” (if you are software tester, software developer, manager)
1️⃣ It’s the first book about the approach the authors have taught for decades—Rapid Software Testing. The more I learned about it, the more I realized I had been practicing some parts on my own, even before I knew about RST's existence.
2️⃣ The book is full of testing terms and techniques. But you can’t skip it. Why? Because on each page, on each term, James and Michael challenge your assumptions. They are asking you: Is it really … like that? Are you sure?
That’s why I have pages of notes left after reading this book. I think I will review them many times, especially as I start practicing approaches (from today).
❓ You may ask: Is it worth reading “Taking Testing Seriously”? I can say - YES.
What exactly can you find inside:
✍ Which cultures of testing are there, and how is RST different
✍ Why testing is a difficult job and how it really differs from programming
✍ What does it really mean … to test
✍ How testing and automation are connected
✍ Which tools can help you test and experiment
✍ How to create a test strategy that really works
✍ How to use AI in testing
✍ How to talk about testing with other people so they WILL LISTEN
✍ What are HTSM, prospective testing, deep, and shallow testing
✍ Tips to apply RST in usability, testability, and signal-based testing
And much more! Including real-world stories from other testers and how they applied RST at work. It is fascinating to read. 🙄
👉 Read this book if you care about testing as a career, as a craft, as a profession.
👉 Read this book to understand that testing is not only about automation and tools.
👉 Read this book if you want to upgrade your knowledge of testing to a deeper level.
💡 P.S. It’s ok to challenge assumptions about RST terms and approaches from the book. By the way, the authors even encourage you to do precisely this. Because that's how the industry is moving forward.
💡 P.P.S. This book is a great choice for a testing book club 🙂