Top critical review
Reviewed in the United States on April 2, 2017
Various organisations approach the testing process differently. Therefore the usefulness of particular tools and books is determined by the context in which the organisation operates. I am testing applications in telecom companies (billing systems, rating, CRM). And I personally find this book almost useless.
It did not help me in any way in my test automation efforts. It makes an impression of providing a thorough coverage of the topic, but when digesting what you've just read, you realise that you still don't know how to start the actual, real, tangible test automation. Sure, test automation is a kind of endeavour, which requires planning. You should spend some time thinking about the potential benefit, potential cost, schedule, required staffing etc. And good book on test automation should warn about all this and devote some pages for covering that stuff. But 350 pages?! Out of 500?
The book misses useful practical details on how the automation should look like. It does provide some examples, but they are so basic, that they can be hardly considered helpful.
I may sound mean now, I am sorry, but I firmly believe in what I am going to write right now, which is: this book is indispensable if your goal is to suck the money out of the customer's pocket, having a test automation as a pretext. It will guide you how to justify the creation of, and how to create, a plethora of professionally looking documents, bringing no or little value in the reasonable test automation effort.
That's how I see it - a tester of business applications in telecom companies. Maybe, there are some branches of the business, where all this fluff is needed and will be highly appreciated. But in my branch - this book is useless.
As a final note: I shared my opinion on this book with my colleague. And he told me something like "Oh come on. Show some understanding and respect. This book is one of the first exhaustive coverage of the topic". Ok. If this is the case, then kudos for the author. The same way as we owe kudos for Graham Bell for his first telephone. But we don't use his first telephone. And we should not use this book as a guide for practical test automation.