Gaining grip on your new automation endeavour can be a challenge, especially when your team is new to the art. Teams can stall due to lack of time, no overall direction, or knowledge paralysis. But you can resolve this roadblock by temporarily bringing on a developer.

The Problems

I inherited a team that had been rooted in manual examination and was in the procedure of adapting automation practices. There are normally 1-2 engineers per scrum team, but they had recently turn shorthanded due to a duo of promotions out of the squad.

The squad began to stall in its automation feat due to:

• Lack of education – The independent person leading the training had moved on.

• Lack of clip – The simplification in resources make many on the team to perform double- duty while awaiting reinforcements.

• Siloed team – There was no architect to provide cross-team way.

• Autonomous scheme – Because the teams were siloed, they were developing with different tech oodles and principles.

• Offshore resourcefulness without proper support – There was not decent time to focus efforts on kickstarting the offshore team.

So with a fully maxed-out team, and company goals to automatise a sure percentage of tests, the squad began quickly falling behind.

Solutions Come From Unexpected Places

In my regular meetings with our director of development, we discuss the need to automate, and the obstacle we faced. Out of the low one day, he approach me and said one of his teams had a spare developer that he could lend me for a twosome of months.

Of course, I jumped!

In less than two workweek, the developer care to:

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

• Meet with the offshore automation technologist and withdraw their obstacles. (It just took some dedicated attention and a little bit of developer suspicion.)

• Review tests written by each squad and establish a common scheme based on development principles.

• Easily clean up stale tryout that had begun miscarry due to lack of upkeep.

• Work across merchandise teams to establish an automation guild, to conform and rede on best practices across the fellowship.

• Bring a voice of experience to the table as the team was ascertain whether it should gift in certain tools.

We now have aKanbanboard where all engineers can post their wish lists for anything from help setting up tool, proficient expertness for tougher tests, and overall guidance.

An Added Bonus

Now that we are making solid progression on our automation goal, we are capable to demonstrate automation ’ s deserving to the rest of the world. As we get draw our tests into the Continuous Integration process, we will increase the speed to release with a higher quality merchandise.

Once we ’ ve established the worth of a dedicated resource with ontogeny skills, we might be capable to leverage this into a new place for the QA team.

At a previous company, I worked on an mechanization effort where we had a grouping of developers consecrate to endorse our huge automation effort. The developers shared that they choose working on the automation squad over the development teams because:

• They be constantly have with new problems to resolve.

• There was ever a new tool to explore.

• They didn ’ t spirit locked into work on long project with a narrow focus of features to code.

I note this to my developer, and certain plenty, he is really bask this. He is in a view to channelise squad, establish scheme, and mostly feel like he is make a valuable contribution to the overall development effort.

“ Mom, can I keep him? ”

If he returns after his time working with us, I know I ’ ll experience a potent friend on the growing squad going forth.

Moral of the Story

Sometimes solution are closer than you imagine. You should reach out to your development team. You might not be as lucky as I ’ ve been, but you may at least see interest from developer willing to make out to lend a hand.

If that fails, consider bringing in a developer on a short-term declaration. My experience has proven to me that it ’ s worth it.

Joe Nolan (@ JoeSolobx) is a QA Team Manager with over 12 years of experience direct multi-nationally place mobile and web QA teams, and is the co-organizer of the DC Agile Software Testing Group (DCAST) Meetup.