Test Automation in the Real World: Practical Lessons for Automated Testing

The book "Test Automation in the Real World" is geared more towards UI level testing and takes about an hour to readThere are several chapters and paragraphs worth highlighting and going back to every now and then. Greg has done a fantastic job of breaking down many of the important stages of starting up and maintaining a successful test system. He has provided just enough depth to address common tools, their strengths and weaknesses, and making sure you consider your test methodology and how a tool can work for you.The book initially covers concepts like tool selection, hiring the right people, requirements for tests and how the team operates. He then expands on the ongoing automation software development process. I appreciate his candor about how hard it can be to do automation right, the patience it takes if you want to build something that lasts, and how to recognize and correct ROI robbers. Leveraging the strengths of the tools, asking the right questions, abstracting code, function libraries, etc.From my perspective, he covers a decent amount of material at a generic level. The writing is deep enough to cause reflection, questions to formulate, and practical suggestions to have success. Perhaps the most interesting reading for me was his list of ROI robbers. I read the list before reading the in-depth descriptions in the chapter. I initially would have said thing are pretty good. Reading the actual ROI descriptions was enlightening because it caused me to reflect on our systems and realize that some things are good, but, it also pointed out where there is room for improvement.Reading with the willingness to listen to Greg's words in this book is valuable for anyone just starting out as well as for veterans of test automation. Well done.

On a testing Slack channel, Greg Paskal answered a question I had as well as providing some great advice on getting started with test automation. It was valuable information and advice, so I wanted to know more about Mr. Paskal. I came across a book he wrote titled, “Test Automation in the Real World: Practical Lessons for Automated Testing” and ordered it ASAP. I read the book this past week, and it did not disappoint. The book is Paskal’s 30 plus years of experience with software development and test engineering, and what has worked for him, as well as some of the mistakes he’s seen along the way with early and inexperienced adopters of test automation. Effective approaches to planning and steps to preventing mistakes that can possibly result in brittle tests and test frameworks, are part of what this book covers. If you are new or experienced, I would highly recommend this book. Mr. Paskal is very reputable in the testing community, no to mention he has the experience to back it up.

When I bought this book, I was expecting practical knowledge that would help me on the job. I was looking for Test Automation in the REAL WORLD! Unfortunately, this book does not deliver on its front-page promise. I was expecting a nice thick book to read, like all the others I have ordered. This one barely cleared 100 pages. It's hard to tell though, because the author did not even include page numbers!! I'm all for Amazon print-on-demand, but this is just lazy (and btw there are 94 pages).Virtually all descriptions provided in this book are extremely vague. The author states that he worked for an "aerospace company." Great. Which one? Where? When? For how long? What was his title? Who did he know there? etc. Give your audience some juicy details, please! I worked in software test in aerospace long enough to know that testers there should probably not be writing books on test automation. Their methodologies are outdated and defunct. It's very clear that this author has developed most of his test automation frameworks in VBA. Try this in the "REAL WORLD" and you will get eaten alive. Today, we test in Python, Ruby, Perl, Java, C#. We need to perform Continuous Delivery and provide real-time test progress and status metrics to stakeholders. We need to integrate with test case managers and know about open-source test runners. You will not learn about any of that here.The worst part of this book is that it contains a number of poisonous suggestions that NOBODY should follow! Ridiculous naming conventions, poor programming practices, and much more. Buy this book and send directly to your competition. It's the only way you will benefit. If you want a solid source of information, start reading the ISTQB syllabi. If you do, you may have hope after all.

This is an excellent read. The book bridges how test automation is marketed, imagined and the real benefits that are available to the skilled practioner who properly wields the tools of test automation. I wish these secrets and this wisdom was available to me before we first tried to implement a tool. Reading the automation evaluation chapter opened my eyes to the possibilities of managing expectations before diving into a project where test automation will have moderate benefit. ROI robbers was a tough read as I realized that we have been paying a lot of ‘stupid tax’. Not anymore though! Take the scholarship, save yourself expensive hard knocks, and get this book.

This book is a gift for those of us of in the testing community. Greg has an awesome ability to take a complex concept and break it down into digestible chunks that are engaging and easy to understand. In this book, he takes us on a journey through his 30 years of work experiences going over the challenges and accomplishments he faced along the way. There are several parts in his journey that I can relate to my own which is an inspiration to indicate I'm on the right path in developing my craft. I highly recommend this book to anyone that has interest in the test profession. It's not often that you get a map of someone’s career that is as experienced and accomplished as Greg. It is also refreshing to read a book from someone that truly loves what they do. It will fill you up with inspiration, and ideas which you will want to bring back to your team to share.