Patterns to Whole-Team Test Automation Transformation
summary
Organization builds a company library called Plexus and moves UI tests from Robot Framework into pytest and Playwright or Cypress so developers actually contribute; pipelines run 213,708 tests per day and teams cut the lead time to reliable from a month to hours. Management sees coverage with repo visualization and an epic-level metric (one team shows 39% epics automated). Practice is ensemble pairing for learning, releasing based on whatever automation exists, and fixing tests as part of the change.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:07BEST PRACTICES CASE STUDY Patterns to Whole-Team Test Automation Transformation
- 0:21Patterns to Whole Team Test Automation Transformation
- 24:13Moving from specialist language to generalist language
- 27:12Visualizing testing debt and coverage
- 30:45Showcase progress made of continuous flow of small changes
- 31:18Choose to release based on automation no matter how little test automation there is
- 33:47Growing individual competencies by sharing YOUR screen when working together
- 39:29Improved Understanding of Success No manual and automated testing Contemporary Exploratory
related talks
18mEffective Test Automation Framework Design
49mReal World Lessons from Scaling Test Automation
21mThe Essential Pillars of Automation Testing for Success
40mScaling testing & test automation without losing control
46mThe Practical Automation Playbook
52mHow to win with automation and influence people
28mEgad! How Do We Start Writing Better Tests?
46mSoftware Devs in Test Automation - Dream or Reality in Agile Software Dev?