I bought Binder's "Testing Object-Oriented Systems" book.
I'm a technical QA, and wanted to both strengthen my test automation skills and become more thorough. However, I found the book so abstract and difficult to understand, that I cannot make any practical use of it. I though it might be my opinion only but I found there are more similar views of experienced software engineers, so maybe there are objective hurdles to read and "apply" this book.
- How do you read this book?
- What problems have you solved thanks to this book?
There are people here who read this book and recommended it, so I believe the book can be useful in practice. I just need to hear how.
I've read a lot of technical literature, research papers, documentation so I was expecting this book will be both useful and legible to me. I am used to literature and research papers that are problem-driven. Books that follow a bottom-up approach, where a reader can build his or her own model of solving certain class of problems, by reading about those problems. This particular book does the opposite, so if someone can show me connection between real problems and the theory laid in this book, I might learn or motivate myself to grab for this book again.