Pipe dream or reality? Mobile web testing in your CI/CD pipeline
summary
Selenium scripts run on mobile with small Appium changes, and Chrome DevTools’ device emulation and window resize command are only a first approximation; Google warns not to rely on them. Three execution choices exist: browser emulation, simulator/emulator, and real devices. Real hardware reveals performance, CPU/architecture and feature differences and is necessary for final validation, while emulation offers speed for early development; USB-tethered real-device labs do not scale and incur management and cost overhead.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:46The good old days
- 2:35The current situation
- 4:13Three options
- 5:31Whats different
- 6:41Other considerations
- 7:37Recommendations
related talks
47mWhat I Learned Building a Mobile Testing Infrastructure
41mPlug Real Devices into Your Jenkins Process and Automate Testing
18mExploration of tools, frameworks to take the pain out of mobile app testing!
19mHow to Leverage mobile app tests for API tests
25mBuilding a scalable device lab with Ansible
34mSetting up Android UI Testing on CI
42mConquer Mobile App CI/CD Challenges Using with a Device Cloud
39mTaming Public Device Clouds for App Testing