How to Get Automation Included in Your Definition of Done – Angie Jones thumbnail

How to Get Automation Included in Your Definition of Done – Angie Jones

21 Dec 2016
  • Locked

While most teams appreciate the benefits of automation, it is commonly viewed as too time-consuming to be considered as part of an agile sprint; resulting in automation being done in isolation and typically months after the story has been closed. There are several problems with this approach. The automation team members are not as familiar with the requirements as team members who were engaged within the sprint, which could result in them missing key aspects while testing. Automated regression testing of the features doesn’t take place until far too long after the feature has been delivered which means more manual regression and/or a period where new features are being introduced but no regression is taking place.

Join Angie Jones as she discusses agile-friendly approaches to test automation which will allow teams to close their sprints with automation in place. These automation techniques allow scrum teams to work smarter, not harder, and find bugs quicker with a more narrowed scope of the root cause, essentially leading to quicker resolution times. Angie will also walk through an example Story and demonstrate how to apply these techniques to ensure automation is achievable within the sprint.


Comments

Sign in to comment
Explore MoT
MoTaCon 2026 image
Thu, 1 Oct
A tech conference to help you navigate the ever-shifting landscape of Quality Engineering, AI, Leadership, Product, Accessibility and Security.
MoT Intermediate Certificate in Test Automation image
Elevate to senior test automation roles with mastery in automated checks, insightful reporting, and framework maintenance
Into The Motaverse image
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.
Subscribe to our newsletter