Cross browser and device platforms are ripe for disruption
summary
Argues that current cross-browser/device SaaS breaks Shift Left: pricing by parallel connections and limited real-device pools make true per-commit testing unaffordable. Presents concrete scale example — 50 teams × 5 people × 30 tests → ~1,500 potential concurrent runs, needing 700–800 parallel connections and costing millions. Proposes an alternative stack using AWS mac1.metal, Android emulators on bare-metal/cloud, Mac mini clouds and K8s/containers to run simulators/emulators at scale, using real devices only for sanity checks.
AI-written summary · about
chapters (9)
- 0:00Start
- 5:20Key Ingredients of a Cdc Pipeline
- 5:47Focused Microset Test
- 7:09Visualize Test Results
- 19:01Desktop Is Still the King of Conversion
- 21:37Why Region Specific Process
- 24:18Evolution of New Technologies
- 30:15Test Pyramid
- 38:24How Do You Groups Tests for Other Browsers
related talks
59mThe Future of automated testing
45mPanel Discussion | Test Automation Trends
44mThe future of test automation
35mElevate your testing: testing smarter, not harder, in the cloud!
18mExploration of tools, frameworks to take the pain out of mobile app testing!
44mThe Future of Test Automation
01h 03mKEYNOTE: SOFTWARE TESTING IN THE CLOUD
30mTesting Mobile Web Apps on Real Devices: How Fortune 100 companies do it