By: Stan Lee Itzcoatl.
Shelfware, overcomplicated frameworks, no automation at all… I’ve seen just about everything in regards to the challenges companies face when trying to incorporate test automation into their groups. In some situations companies do not know how to even start an automation process. In many other cases companies purchase tools that no one ever uses. This is the classic shelfware situation. In the points below I’m going to share with you what it takes to implement and sustain a successful test automation process.
New Culture
Test automation is a culture not an assignment. It is not a task that can be checked off as fully done and then disappears from your to do list. To be successful it has to be treated as a new and permanent culture. QA and development will need to work closer than ever. You will need to create a culture whereby your teams are constantly talking about automation and not considering any testing assignment completed unless there is supporting test automation. You will need to setup weekly automation meetings to initially train your staff and later to discuss creative ways to continuously improve things. Most importantly, the automation culture must be fun!
Create Realistic Goals
Set realistic automation goals so that you can see progress being made. Trying to automate 500 websites by end of year sounds ambitious to management, but to the rest of the team it will be a red flag that you do not understand the level of effort. So in the end it will have the effect of lowering morale on your team since they will feel hopeless to meeting such an unrealistic goal. Instead, plan properly by setting short and long term goals for automation. Target what needs attention immediately. Set a realistic long term plan by not over-promising to the leadership. Set goals that you know you can reach and give your team breathing room. There’s nothing wrong with setting high expectations for your team, but if you make unrealistic test automation promises to the executive team you will lose the support of your staff.
Select the Right Tools
When it’s time to select an automation tool and framework do not try to be the group that goes for the sexy new tool/framework that just popped up. Another possible pitfall is to select a tool that has been around a long time but that hardly anyone in the industry uses. You want a tool that is both used heavily in our industry and one that has been around a few years. This will make it easier for you to a) find new resources when your staff moves on and b) find support from online groups and help boards.
The Right Framework
Automation frameworks can have all sorts of bells and whistles but the truth is that if normal people cannot use it then it will become shelfware. I’ve worked at a number of companies where I joined and the existing automation framework was so complex that no one used it. There were also cases where only the automation lead used it. Both cases are not acceptable. Your framework should allow all QA and development members to contribute scripts easily. The contributions might come after some simple tutorial sessions or some coding walkthroughs. That is fine, but if you see that even developers are having a hard time contributing then it’s time for a direction change.
Lead by Example and Embrace Creativity
Without a doubt I’ve seen the most success in automation when leaders (QA Managers/QA Directors/Development Managers) lead by example. This can come in a few different forms. The first important thing is to be at the forefront of training your team and making it a continuous process. The second thing is to set the tone by making it clear to the QA team that everyone is expected to contribute. This means technical and non-technical folks. Technical QA engineers can obviously do awesome work with coding and setting up your framework. Non-technical QA engineers must understand the framework, know how to execute it, and know some scripting basics. Establish coding standards but also allow some room for creativity and new ideas. Your team will love providing their input.
Track your progress and reward people
Since we already mentioned that it is important to create realistic goals, it will be equally important to track them. Tracking your progress will be both challenging and one of the most rewarding things you’ll do in your automation culture. It’s rewarding due to the progress you’ll be making. You will see short term goals completed and you will see long term goals start to make progress. It will be exciting! Share your progress as a team (QA, development, etc…). Find ways to inform upper management of the great progress being made as well. Find ways to reward team members for their contributions and support. After all, you cannot be successful without their hard work and support.
In closing, I want to stress that all of the above are good strategies but nothing will work if you do not create a fun and energetic environment. Automation is hard work and it can take a toll on your staff. Automation is also fun and should be done within a fun environment. Do your best to make things enjoyable.
Stanitz LLC offers modern test automation and a full set of Quality Assurance services. If you need test automation introduced into your company or if you need to improve your existing automation framework contact Stanitz to discuss the exciting possibilities.