Why testing is a developer's problem

on YouTube ↗32m

" summary

Argues that test automation must match Agile speed and shows a working solution: Testim/Testm with a virtual mobile grid, record‑and‑replay authoring, variable injection from CSV/JSON/Excel, and CI hooks (GitHub Actions/Jenkins/Azure). Claims 60–80% of testing stays manual, maintenance eats ~30–40% of test time, and ML locators with adjustable thresholds cut flakes so tests survive UI and device changes. Demo runs on emulators or real device clouds, parallelizes runs, reports failures to Jira, and returns performance metrics.

AI-written summary · about

" chapters (7)

1. 0:00Testing as team responsibility
2. 4:55Testing in DevOps bottleneck
3. 6:40Manual vs open-source testing
4. 9:28Low-code test automation
5. 14:44Testim mobile testing demo
6. 29:18Testing business impact
7. 31:05Closing remarks

" related talks

• 23mWhy testing is also a developer's problemBlake Reynolds, Eric Hastie · droidcon New York 2024
• 45mPanel Discussion | Test Automation TrendsYevheniia Hlovatska, Thomas Carpentier, Ellinor Kwok, Kerim Satirli · TestCon Europe 2021
• 55mShifting the Testing Role PendulumMelissa Tondi · CAST 2016
• 53mTest automation for developersArnon Axelrod · .NET Fest 2019
• 18mExploration of tools, frameworks to take the pain out of mobile app testing!Syed Hamid · droidcon London 2022
• 01h 08mTest Automation MonstersPhil Royston, Marcel Veselka · TestCon Europe 2021
• 51mRedefining test automationRichard Bradshaw · SeleniumConf London 2019
• 41mHow AI is transforming software testingRaj Subramanian · SeleniumConf Chicago 2018