The Digital Divide and Test Automation
summary
Framework frames team contribution as a Venn of access, skills, motivation and maps roles like teachers observers advocates to concrete outcomes: Team 1 (bank) ships a stable low‑level DB retrieval suite that works but lacks business input; Team 2 (consultancy) produces elegant tests but sparse coverage and a growing backlog because the coach lacks repository access; Team 3 pairs BA + tester for good coverage; Team 4 has no automation without an advocate. Cites 6 million Germans offline and seven people with >1,000 Selenium commits; mentions Jenkins and Selenium.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:05Katrina Clokie
- 2:04My first hockey team
- 3:07No hockey gear
- 3:44Getting onto the field
- 4:33Schooling
- 6:07Internet Access
- 7:33Access Not Use
- 8:50Digital Divide
- 10:22Sheep
- 12:05Division Test Automation
- 18:35Skills and Motivation
- 26:57One Thing to Change
- 28:07Peer Review
- 28:49Impact on Test Automation
- 30:37Conways Law
- 32:10Step Back
- 32:58Access
- 33:55Skill
- 34:55Motivation
- 35:45Who isnt inside your fence
- 36:55Recap
- 38:40My role
- 39:26Weapons of change
- 40:48Conclusion
related talks
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
46mPanel Discussion | Building Strong Testing Teams: Management, Development, and Diversity
49mWelcome to the Future! Preparing for our Agile Testing Journeys
40mThinker, Tester, Lawyer, Spy
41mWorking With Developers: A Tester's Survival Guide
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
01h 48mNo Such Thing as Manual Testing and Other Confusions
47mThe Importance of Soft Skills in Test Automation