In my last post, we talked about where and when you’re likely to be running tests, depending on the automation stage you’re in. Today, for my final topic in this series, I will cover something really important: how you can motivate your team and get people to join you on your journey to automation.
First, look in the mirror
Before you can motivate your team, you have to start by motivating yourself! I recommend you begin by devoting some percentage of your time to training, with the intention of ultimately being able to spread the knowledge internally. Industry conferences and events are great, but there are also plenty of websites and online testing chats to get ideas and support, including Ministry of Testing, TestGuild, and Sauce Labs, among others. By dedicating yourself to education and training and making an effort to share what you learn, you will start to become an agent of change within your team.
Technology is ever-changing. If you don’t motivate yourself and commit to learning and growing, you risk stagnating in a fast-moving field. This is true of any tech job, but in testing specifically, not learning and growing will mean you miss opportunities to improve testing and make yourself valuable to your organization (and therefore to future employers, too). Who wants to end up getting bogged down in repetitive testing tasks? Not me—and I bet you don’t, either.
Motivating your immediate team
Okay, so what can you do to get your coworkers on board? Start by testing earlier. Pair up with the developers and see if you can work together to find better ways to test features. Track progress using reports and dashboards, and use them to show progress to the team and get people on board. Also, create simple guidelines on what to test and what to expect from testing, and train folks internally to help people improve.
Don’t get caught in a “Dev vs. QA” mindset. You want clear roles with solid collaboration—not confusion and finger-pointing. Siloed organizations can break communication and ultimately create an environment where there’s low trust in automation.
Motivating your organization
My biggest piece of advice here is however you can, connect business success metrics with testing. Can you document how finding a bug in production reduced revenue, then show how finding it earlier protected your organization’s revenue stream? Do a proof of concept showing how testing can be a business enabler. Increasing automation can help you increase release frequency and speed, as well as product reliability.
In the end, treating testing as an afterthought can harm user experience and reliability. But investing in the time, training, and processes that enable automated testing can help your entire organization grow and scale.
If you enjoyed this post, check out the previous installments of Diego’s “5 Steps to Jumpstart Test Automation” series:
Part 1: Introduction
Part 2: Team Setup
Part 3: Testing Framework
Part 4: How to Test The Right Things
Part 5: Where (and When) to Run Tests