Why testing is also a developer's problem
summary
Argues that developers must own end‑to‑end testing because QA bottlenecks slow releases and Appium maintenance consumes ~30% of tester time. Shows a low‑code mobile platform (upload APK/IPA, record-and-playback, device grid) that builds reusable steps, data drives tests, and posts Jira bugs. Claims proprietary machine-learning smart locators adapt to UI changes (demo migrates a flow across versions and a dark theme) so web is very resilient, mobile still somewhat brittle, import of old tests is discouraged.
AI-written summary · about
chapters (9)
- 0:00Testing bottleneck
- 1:05QA struggles with E2E testing
- 3:13AI-powered testing solutions
- 4:57Demo: Testm mobile platform
- 13:00Tests in CI pipelines
- 17:54AI adapts to UI changes
- 19:39Benefits for devs and QA
- 21:04Mobile testing challenges
- 22:28Migrating from Appium to AI
related talks
32mWhy testing is a developer's problem
24mMastering the mobile testing pyramid
18mExploration of tools, frameworks to take the pain out of mobile app testing!
44mTest what?
18mReinventing App Testing with Agentic Apps
43mUI testing is so easy - said no developer ever
46mTowards Joyful Development
44mEfficient testing UI Android apps by example