Frictionless Android testing: Write once, run everywhere
summary
Claims a single, canonical API set so tests run on-device, off-device, or in Cloud with no rewrites, and cites billions of existing test invocations. It packages Android JUnit4 Runner, activity test rules, Espresso and Espresso‑Intents, Robolectric support, Truth extensions and Android Test (Jetpack) data builders to reduce boilerplate, and ships a test executor called Project Nitrogen that uses Android Orchestrator and Android JUnit Runner to isolate runs. Robolectric 4.0 is released and Google reports internal use on Gmail, Maps, Photos and YouTube.
AI-written summary · about
chapters (22)
- 0:00Start
- 1:27made up of three layers unit integration and end-to-end tests
- 1:59produce a holistic automated testing environment
- 4:08break tests down into three clear sections
- 4:56use common setup methods only for scaffolding
- 5:11highlight this using a simple test case
- 6:24stub out some of the android framework behavior in the superclass
- 7:03execute your code
- 9:56building up your entire apk deploying it to the device
- 10:49use the espresso view matcher
- 12:36focus on writing your tests rather than considering those tools and libraries
- 15:23set up your test environment
- 16:28make assertions on the state of the system
- 18:34run the test either on device on your local workstation
- 19:51start with a simple test for our business logic
- 20:06adding an integration test
- 21:01refactor this large complicated test refactoring a large test
- 22:51run the entire test suite on our continuous integration server
- 26:08prepares the device for the next step test execution
- 26:36running a unit test on your local workstation
- 32:50accelerate your testing experience
- 33:46submit your feedback
