How to win with automation and influence people
summary
Organization inherits nine frameworks with UI tests abandoned for 18 months, unit tests missing and CI builds taking ~30 minutes due to slow flaky end-to-end tests. Team runs a one-week framework challenge, selects Gauge + Java by vote, implements 13 smoke tests and cross-discipline pairing, plus a TechRadar gate and a testers’ guild. API test choice (Unirest) and Siren JSON parsing cause ongoing rewrites, but feature squads, code review and pairing produce a workable multi-team automation platform and rising unit-test adoption.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:33Architecture of the system
- 4:38Clunky front end
- 7:37BDD Frameworks inside BDD frameworks
- 16:04The API Acceptance Tests
- 21:07Refactoring was scary
- 23:28Cucumber vs Gauge
- 26:12Component teams weren't working
- 32:05Everyone knew it was a sales pitch
- 42:19Any questions?
related talks
18mEffective Test Automation Framework Design
40mScaling testing & test automation without losing control
05mTaming the Testing Beast
43mTransformative Culture
38mScaling Automated Testing & Architecture from Startup to Enterprise
13mThe Automation Firehose Be Strategic and Tactical
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
36mContext-driven Agile Tester