What is a Proper Agile Iteration (Sprint)? Part 4: Continuous Testing

E2E Test Automation is backbone of Agile/DevOps. Without solid automated regression testing, how can it be real Agile?

Non-Medium Members: You can read this article for free on “Agile Way Newsletter” (Substack)

I share my view of “Proper Agile Iteration (Sprint)” in this series:

• Part 1: User Story *
• Part 2: Testing and Coding *
• Part 3: Done Done *
• Part 4: Continuous Testing
• Part 5: Showcase (upcoming)
• Part 6: ‘Production’ Deployment (upcoming)
• Part 7: Sustained Pace (upcoming)

(I have applied the above in some client projects I led and all of my own app development, with great success)

Clarification: The testing in Continuous Testing (CT) means “Automated End-to-End (UI) Testing,” not unit testing. Unit testing is typically part of a traditional CI process, such as running JUnit tests (aka, programmer tests) in Jenkins. Managing Automated E2E (UI) tests, however, presents a far greater challenge.