Code Quality on Android - A grumpy old man's perspective

on YouTube ↗38m

" summary

OneView enforces build and quality gates with Jenkins, runs static analysis with SonarQube (plus Detekt for Kotlin) and requires heavy unit testing: about 80% of tests are unit tests, integration tests cover flows, and instrumentation tests stay minimal. Unit tests use Mockito and RxJava helpers; view tests use Robolectric to avoid slow emulators. Code uses constructor injection, builders or Toothpick for test doubles. A CI fail on coverage or Sonar rules blocks merges; a fake test once let a bug reach production.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 4:50Don't let premature optimization replace readability
3. 6:54Setup a CICD server
4. 8:08Use a static code analizer
5. 11:13Code reviews
6. 15:23How do we approach testing?
7. 16:15Test a single method of a single class
8. 30:45A grumpy old man's perspective

" related talks

• 19mEase Software structural quality on Android (en)Vincent Brison · Droidcon Paris 2015
• 45mComputer Says No - Static Analysis and CI in a Kotlin WordSebastiano Poggi · App Builders Switzerland 2019
• 36mAndroid like a (reliable) Rock Star - All About Android Continuous IntegrationMark Scheel · droidcon San Francisco 2017
• 41mFirst, Do No HarmAnnyce Davis · Android Summit 2017
• 26mAndroid CI: 2016 editionYusuke Yagyu · DroidKaigi 2016
• 20mUnit testing on AndroidBuşra Deniz · droidcon Berlin 2015
• 21mMastering Code Quality: A Deep Dive into Custom Linting for Android DevelopersGopal · Android Worldwide January 2024
• 53mCI for Android Using JenkinsSam Edwards, Dan Jarvis · Android Summit 2016