One test suite for instrumentation and Robolectric tests

on YouTube ↗35m

" summary

Claim: one test suite runs on device/emulator and on the JVM using Robolectric. Concrete tools and steps: copy or share tests via a shared test folder, add Robolectric and testImplementation deps, use Gradle tasks (connectedAndroidTest vs testDebugUnitTest), and implement environment-specific helpers like an airplane mode toggler (UIAutomator on device, Settings shadow + broadcast on Robolectric). Built a Robolectric shadow activity to launch secondary screens; it works but needs manual cleanup and IDE workarounds. Speed wins: examples show ~1 minute on Robolectric versus ~3+ minutes on emulators and orchestrator sometimes inflates runs toward an hour.

AI-written summary · about

" chapters (10)

1. 0:00Unified testing approach
2. 3:16Device test execution lifecycle
3. 6:48Robolectric overview and benefits
4. 9:18Robolectric history and evolution
5. 11:22Running Robolectric tests
6. 13:48Shared test folder challenges
7. 16:38Multi-activity testing
8. 24:05System interaction testing
9. 31:13Device vs Robolectric tests
10. 34:25Should you use Robolectric?

" related talks

• 46mEfficient Android UI TestingAlex Zhukovich · droidcon Italy 2021
• 41mAndroid Testing BootstrapFlorent Noël, Sylvain Galand · DevFest Paris 2015
• 34mFrictionless Android testing: Write once, run everywhereJonathan Gerrish · Google I/O 2018
• 44mWhat makes good unit tests for Android appsNozomi Takuma · DroidKaigi 2023
• 42mProduction Level Test Driven Development and What's newKapil Bakshi · GDG DevFest Ahmedabad 2017
• 35mTesting Firebase Android SDKs at GoogleGrygorii Luchytsky · Android Summit 2018
• 20mUnit testing on AndroidBuşra Deniz · droidcon Berlin 2015
• 41mUnit Test Your Code, Even Your UI!Stan Kocken · Droidcon Paris 2015