To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzes reviews to verify trustworthiness.
It is a great book that covers test automation for actual enterprise software. It does not concentrate on the new shiny cloud based microservice tech of the week, but instead offers a comprehensive overview of test automation for actual large brown field projects with its legacy code, messy dependencies, msi installers (yes, more than one) on an actual DVD, unmaintained and broken automated tests written by that intern from two years ago, undocumented and forgotten features that one customer might still be using somewhere, etc. It's a book for taking the messy real world and bringing it step by step closer to the unicorn world with perfect test coverage and a team that uses those tests to accelerate and drive feature development.
On the negatives, I found many typos and incorrect sentence structures that break the flow of reading for me. It's not that bad, but it is annoying to stop mid-sentence and have to re-read it because a word was missing or something similar once or twice every chapter.
But don't let the form keep you away from the content. It helped me answer many questions like what types of tests should we begin with (Integration tests? Synthetic tests? Acceptance tests?), what to mock and not to mock depending on the type of test, who should develop the tests in our organization, what benefits should we expect, etc. I will definitely refer to the wisdom in these pages for years to come.
The Good: - The Software-Example is nice, and it works properly with git. I have rarely seen that good maintained examples. That said, the example itself is ... quite big, so one has to like it, but its still a pro-point. - The advices for how to get your team to testing are very good. - The advices always care about budget
The Bad: - Some statements are really bad when it comes to e.g. what object oriented programming is. While this book is not about programing languages, it should have maybe just been left out (or quoted from something ... more reasonable) - Some of the Images are huge and the book could be a little shorter otherwise - Parts are very lengthy and redudant. It could be shorter. - There are little to no metrics presented, how to measure the effect and therefore success of testing. This should be a critical part of this book.
In Addition, some books just cover some things better. E.g. When it comes to testing and the CI/CD Part one should rather read another book, such das Continous delivery, and leave this one be. This book is for someone really getting started as a non-developer. For everyone else I think it lacks depth.