As an automation tester, I always found it challenging to demonstrate the value of automated testing in the development lifecycle and how to connect testing directly to customer outcomes. The general perception is that more time is spent running automated tests or troubleshooting broken tests than gaining actual benefits. What if, instead of just building automated tests, we treated automation testing as an assumption that needs validation?

My topic centers on my experience of “testing the testing.” By establishing clear objectives and key results (OKRs), I set the right expectations for automation testing. Lean experimentation helped me validate or refute assumptions about implementing automation testing, considering the complexities of the company, people and its environments.

Takeaways from your talk: 1. OKR’s for testing

2. How to identify Leading vs lagging (What actually moves the needle )

3. Lean experimentation to validate assumptions of testing

4. establish visual management system to track progress and results