Unleashing the Power of Remote Tooling
summary
Layered local testing includes developer builds, unit tests, screenshot diffs and end‑to‑end plus team playtests, but real issues still appear in production. Three concrete case studies: a Moshi migration crashes due to a missing ProGuard keep for adId saved in SharedPreferences and is hotfixed after symbolicated stack traces; a concurrency bug with Room and coroutines exposes DB locks and is solved with breadcrumbs, a mutex, Room autoclose and a per‑feature DB; Chrome Custom Tabs timing is measured by a custom non‑fatal event and iterated rapidly by repurposing A/B framework. Tips: upload mapping file, avoid PII, and include a remote kill switch for verbose logs.
AI-written summary · about
chapters (6)
- 0:00Remote debugging on mobile
- 1:04Local testing approach
- 4:56JSON migration to Moshi
- 10:58Fixing concurrent crash
- 21:51Chrome Custom Tabs integration
- 29:38Recap and future plans
related talks
29mCustom Dev Tools to Supercharge Your Team's Productivity
57mPanel 7: Testing and tooling
48mMobile debugging
27mDeveloper Experience: It’s Time to Start Complaining
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
51mAutomating to augment testing
32mDeveloper Productivity – DIY (with ChatGPT).
44mRemote Mob Programming In a High Stakes Environment