Have you ever wondered what it must be like to find the Rosetta Stone to decipher the Egyptian hieroglyphics? That this what this book is all about A Journey Through Test Automation Patterns: One team’s adventure with the Test Automation Patterns wiki by a Seretta Gamba and Dorothy Graham.
It’s like finding the Rosetta Stone for test automation.
Main Focus of the Test Patterns Book
The main focus of this book is all around automation test design patterns. I recently interviewed Seretta Gamba on my Test Talks podcast all about the book and asked her what tests automation patterns are?
She described them as a simple solution that someone else used and it worked and not only did it work but it’s been successfully used over and over and over again.
So these are known patterns that are known to resolve a lot of issues that you might be struggling with.
The book covers over 86 patterns of 55 common issues automation engineers will face. And all this info is documented on their wiki page. So I’m sure the list will grow over time.
Test Automation Patterns Book is Tool Agnostic
One of the good things about this book is
Format of the Patterns in Automation Book
The book is broken up to five main parts.
Part 1 is a story around a tester named Liz and her journey to discovering and implementing the test automation patterns. It’s written in a story format that’s going to engage you and until the characters are fictional the situations and all the struggles with automation that the character encounters are based on real behaviors that I personally see myself.
The book also includes Part 2 which has mind maps that breaks out all the different patterns and issues into certain areas.
Part 3 covers all these issues and details.
Part 4 Is patterns and the details of all the different models you will encounter in automation.
And in Part 5 is about Diagnostic. So how to diagnose the different issues you’re probably struggling with your exact problem for your test animation project.
Automation Diagnostic Method
The diagnostic piece is critical and the one that Seretta brought up in our podcast interview.
She described as the diagnostic an idea she got from one of her medical doctor friends. He explained to her that when someone comes in that, they don’t know to find out what illness the patient is suffering from they have a set of questions that they ask.
The trick is to ask these questions and based on those questions they able to generate more questions based on their answers. So the first general questions lead to some other questions and these questions to other more specific questions all based on the responses from the patients. Depending on the answer the next set of question will be different.
The beauty of it is you don’t need to ask them many questions to start pinpointing precisely what your automation might be suffering from.
So let’s take a quick look at the wiki to see how the diagnostic works that is outlined in the book itself.
So here’s the first set of diagnostic questions.
Let’s click on we’re struggling with where to satisfy our current automation we’re having issues and want to improve or revive an existing test automation project we’re working.
So click on the first option.
This is then going to show seven other options or questions you can ask. So what what’s the most pressing problem you need to tackle at this moment?
So it might be that you’re struggling with a lack of support. From either management, testers, developers.
So click on the first question first option, and this brings up another set of questions. Next, more specific question based on your previous answer is What were you lacking? What areas do you think you’re lacking in? Most teams struggle with and what I’m struggling with is developers don’t help their own teams. Let’s click on this.
So there are few patterns that usually come up with developers don’t help automation teams. The first one is poor communication.
If you click on an inadequate communication that will data bring up the communication issue that talks about the issue and examples with questions you can ask and also a list of patterns you can use to resolve it.
So a popular one is this whole team approach. Click on the whole team approach and we’ll go over once again the pattern, what it’s about, the description, how to implement, potential problems and all other issues addressed with this pattern.
As you could see with just a few high-level questions we were able to drill down into a specific actual piece of advice.
Why Test Automation Patterns Book Is a Must Buy
So that’s what this book is all about. It’s going to save you a lot of time a lot of effort, and I think it’s going to help a lot of teams so definitely check it out: A Journey Through Test Automation Patterns: One team’s adventure with the Test Automation Patterns wiki by a Seretta Gamba and Dorothy Graham. I think it’s a must read to me with tech.