Augustin Gottlieb

How to add test automation to your project: The good, the bad, and the ugly

What if your test automation strategy was a catalyst for collaboration, not just another QA task?

How to add test automation to your project: The good, the bad, and the ugly
#1about 4 minutes

Setting the stage for a test automation project

A test manager joins a mobile project to introduce end-to-end automation for regression testing with a mixed-skill team.

#2about 4 minutes

Using automation as a catalyst for team collaboration

End-to-end automation can start a conversation between QAs and developers, leading to better testability and shared quality ownership.

#3about 2 minutes

Accelerating feedback loops with mandatory checks

Implementing mandatory automation checks and visible dashboards provides rapid feedback on product health and enforces team discipline.

#4about 2 minutes

Providing security by automating critical bug coverage

Automating regression tests for critical bugs provides an early warning system and traceability for stakeholders.

#5about 3 minutes

Creating more time for valuable exploratory testing

Automating repetitive regression checks frees up QA time for more creative and valuable activities like exploratory testing sessions.

#6about 3 minutes

Avoiding the spare time and automate later fallacies

Automation must be treated as planned, estimated work within a sprint, not an activity for spare time or after a sprint ends.

#7about 2 minutes

Accounting for the hidden cost of test maintenance

Failing to budget time for test maintenance and refactoring leads to framework decay, so it's crucial to plan for it and enforce code reviews.

#8about 2 minutes

Ensuring a stable environment before starting automation

Starting automation on an unstable environment creates flaky tests and erodes trust, so establishing prerequisites for test data and environments is essential.

#9about 2 minutes

Managing expectations and fitting the framework to the team

Avoid project failure by setting realistic expectations about what automation can achieve and selecting a framework that matches your team's existing skills.

#10about 2 minutes

Final warnings: listen to your team and have a strategy

The ultimate failure points for automation are ignoring team feedback and lacking a clear, documented strategy for what you are trying to achieve.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

From learning to earning

Jobs that call for the skills explored in this talk.