Test Automation as a Team Responsibility
Raluca Vartic

Perhaps you have tried automating tests in the past, but ended up with an intimidating number of UI tests that take hours to execute. Although you’ve been maintaining the tests for months, you’ve never once seen them all pass. Most test failures are not defects, so despite having started with enthusiasm, you're beginning to question whether automating the tests is paying off. When quality and test automation are embraced as a team responsibility, automated tests can be worthy team allies. Tests will be fast enough to be executed for every code change, and prevent regressions. When testing efforts are supported by a strong suite of well maintained and consistently passing tests, new features can be frequently released with confidence. On my journey, I have encountered some myths that keep automation work segregated from the rest of the project work. I will present arguments for busting them. Oh, and I will also tell you why I am not afraid of losing my job to robots.

Learning Objectives
- Understand the trade-offs when planning whether test automation will be performed by the team developing the product or by a separate team.
- Learn strategies for engaging agile teams in the automation efforts.
- Improve the visibility of technical tests, in order to build trust in lower level tests and reduce the number of expensive tests.
- Work as a team to optimize the testing plan to catch and prevent issues early, before they become defects.
Learning Level
Session Type