Nitrogen in your (test) pyramid.
summary
Shows a concrete way to run the same Espresso UI tests on the JVM and in CI by adding the instrumentation test sources to the unit-test source set and using Robolectric 4.0 + androidx.test 1.0.0 so Espresso, ActivityScenario and ApplicationProvider work in JVM runs. Uses MockWebServer stubs, Truth assertions and Gradle scripts or JUnit categories to handle many build variants. It mostly works but Robolectric still fails on async/reactive flows, FragmentManager transactions and some custom views, and test-reporting/debugging require extra setup. Project Nitrogen is the unifying goal.
AI-written summary · about
chapters (9)
- 0:00Introduction and legacy code challenge
- 3:03Test pyramid structure explained
- 6:12Android test library overview
- 10:51Unified testing with Robolectric
- 13:03Live code demo setup
- 18:54Running tests in CI with Robolectric
- 21:02Handling build variants in tests
- 23:30Robolectric limitations and fixes
- 24:54Future of unified testing
related talks
51mNitrogen in your (test) pyramid.
34mFrictionless Android testing: Write once, run everywhere
38mGetting Started with AndroidX Test
40mTesting Android apps at scale with Nitrogen
42mRock-Solid UI and Instrumentation Testing
41mAndroid Testing Bootstrap
35mJunit5: the next gen of testing, don't stay behind
46mEfficient Android UI Testing