Test Automation - A Systems Thinking Approach

on YouTube ↗48m

" summary

Claims that test automation fails when it’s done downstream and treated as QA’s job, and shows a concrete alternative: drive design with executable specifications written as Given‑When‑Then examples, implement small example interpreters, and run those examples during development. Demonstrations use Robot Framework and FitNesse as keyword-driven backends, extract a should we notify component for direct, fast tests, and report that this breaks the vicious cycle and makes automation sustainable.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 1:48Test & Fix "Battleship"
3. 2:29The Agile Test Problem
4. 7:105 Why's of Test Automation Being Hard
5. 13:53Example-Driven Development
6. 22:45Test Automation Pyramid
7. 23:32Behavior Specification at Right Level
8. 32:30Life Cycle of an Example
9. 37:18Strategy without tools is

" related talks

• 38mDo We Really Need A Test Automation Engineer?Bas Dijkstra · PNSQC 2024
• 30mConfessions of a Serial Automation QAKateryna Chernikova · Selenium Camp 2020
• 51mRedefining test automationRichard Bradshaw · SeleniumConf London 2019
• 44mTest Automation as a Development TeamSemen Vyazemskiy · TestCon Moscow 2020
• 24mWHY ARE WE FAILING WITH TEST AUTOMATION?Zoltan Kundra · HUSTEF 2015
• 47mWhat Successful Test Automation is... and Why it's NOT Testing!Lee Barnes · TestCon Europe 2022
• 42mOpening Keynote: Blunders in Test AutomationDorothy Graham · TestCon Vilnius 2018
• 53mTest automation for developersArnon Axelrod · .NET Fest 2019