Common pitfalls in mobile testing

on YouTube ↗18m

" summary

Gives concrete failures: tests that only assert simple return values, coverage jumping from ~5–6% to 90% coverage but meaningless by merely calling methods, and tests that verify implementation calls instead of behavior. Shows tools and fixes: Retrofit interceptors, Mockito spies vs real request inspection, Robolectric shadows (for example Robolectric shadow content resolver and Apache HTTP interception caveats), Appium page objects to separate instrumentation from assertions, avoid singletons/static methods, prefer dependency injection (Dagger) and don’t use PowerMock as a design crutch.

AI-written summary · about

" chapters (5)

1. 0:00Intro
2. 0:42Brief history
3. 10:32Know your tools
4. 11:59Only test code
5. 15:29Static code

" related talks

• 44mWhat makes good unit tests for Android appsNozomi Takuma · DroidKaigi 2023
• 41mHow to Really Test an Android ApplicationThomas Guerin, Benjamin Lacroix · Droidcon Paris 2015
• 56mTesting for Success in the Real WorldDonn Felker · Android Summit 2019
• 45mWhere do the Android tests belong?Nazneen Rupawalla, Vidhi Thakrar · droidconIN 2015
• 31mBeyond the Mockery- Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon New York 2023
• 41mAndroid Testing BootstrapFlorent Noël, Sylvain Galand · DevFest Paris 2015
• 24mMastering the mobile testing pyramidLaurent Sigal · droidcon New York 2022
• 44mEfficient testing UI Android apps by exampleAliaksandr Zhukovich · Mobilization 8