Mobiconf 2018: Miroslaw Stanek, Azimo
summary
Claim: move from monthly to release weekly cycles while keeping crash‑free users above 99.5%. Achieves this by automating build/distribution (Gradle, Fastlane plugins), CI that runs emulators and tests every 24 hours, Python scripts for translations, and an open‑source test runner automation supervisor. QA is staged (fast unit feedback, integration with mocked data, end‑to‑end limited to two hours). Unit tests reach about 50–60% coverage, 40 releases in 12 months, and a stop‑the‑line rule for blocking defects.
AI-written summary · about
chapters (12)
- 0:00Introduction to fail fast
- 1:52From monthly to weekly releases
- 7:03Automating build and distribution
- 11:24Optimizing QA process
- 15:19Unit and integration testing
- 21:01Roadmap for QA automation
- 23:16Writing testable code
- 27:18Choosing architecture patterns
- 30:07Code generation and DI
- 33:41Modularizing the codebase
- 36:13People and stop the line rule
- 39:16Q&A session
related talks
38mIterative Mobile Development
39mMobile Developer Productivity Panel
36mIterative Mobile Development
29mOur Journey to Fully Automated Weekly Releases
38mScaling Automated Testing & Architecture from Startup to Enterprise
17mStreamlining Mobile Releases
30mClick-free releases & the making of a CLI app
48mMobile Developer Productivity at Scale