In-Sprint Test Automation Clarified

This term is unnecessary, shall be always doing that in real test automation and real Scrum.

This article is one of the “IT Terminology Clarified” series.

I recently read two articles (#1, #2) mentioning “In-sprint test automation”, its definition is as below:

The user stories developed in the same sprint are verified by automated end-to-end tests.

The benefits of In-sprint Automation are obvious, testing early is always welcome.

Table of Contents:
· In-sprint Test Automation should always be the case in real Agile
· The most effort is not on the stories in the current sprint, but rather regression testing
· How to succeed “In-sprint Test Automation”?

In-sprint Test Automation should always be the case in real Agile

However, I think the term “In-sprint Automation” is unnecessary, as already implied in ‘Done, Done’. I have been performing ‘In-sprint test automation’ since 2006, 16 years ago. If not automated testing user stories immediately after they were implemented, that’s Waterfall, IMO, at least from a testing perspective.