Mobile Testing: Pinpointing Invisible Problems
summary
Mobile app retention is harmed by performance issues like slow startup (>2s), battery drain, memory leaks, and excessive network calls. Practical techniques shown include faking large responses with Charles Proxy to reproduce truncated-history bugs, using Monkey Exerciser for long stress sequences to find crashes and leaks, and diagnosing battery and memory problems with Battery Historian and Android Profiler.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:55Mobile app usage stats
- 4:08Why users delete apps
- 5:54Mobile app performance metrics
- 8:02Charles for network analysis
- 11:15Device startup battery
- 14:10Monkey Test Runner
- 20:55Battery Historian energy analysis
- 27:52Android Profiler memory network
- 31:02Memory leaks detection
- 33:12Performance testing checklist
- 34:38Summary
related talks
06m"Mobile App Performance Testing"
23mMobile App Crashes in Production: Lessons Learned from a Tester’s Viewpoint
18mCommon pitfalls in mobile testing
45mUncovering breaking changes behind UI on mobile applications
24mMastering the mobile testing pyramid
44mEfficient testing UI Android apps by example
41mHow to Really Test an Android Application
18mTesting and Monitoring the Smartphone Experience