Automation does not replace collaboration
summary
Argues that automation supplements rather than replaces team collaboration, using Selenium-style end-to-end tests that create a new user in under two seconds but can be flaky and slow (examples taking three to four seconds), contrasted with unit tests that run in fractions of a second. Demonstrates a workout-log signup built front end → API → database where visual misalignment (inputs shifted right) and an IE11 gap escape automated checks, so paired requirements, trio conversations, and targeted test strategy fix the gaps.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:51Purpose of automated testing
- 3:57Goals of writing tests
- 6:41Types of automated tests
- 9:55Testing a user story example
- 14:15Limitations of automated tests
- 15:37Better requirements through collaboration
- 17:24Catching visual and browser issues
- 19:12Test strategy and efficiency
- 22:03Improving team velocity
- 24:13Why collaboration matters
- 26:20Summary and Q&A
related talks
51mRedefining test automation
01h 08mTest Automation != Less Testers || Faster Testing || More Time For ET
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
07m"It is not automation when..."
01h 08mTest Automation Monsters
33mMore Than Automation: How Good Acceptance Test Can Make Your Team Happier
21mThe Essential Pillars of Automation Testing for Success
16mIsn’t Test Automation a Silver Bullet?