Test your Robolectric knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is a reasonable justification for the significant SPEED advantage Robolectric-based tests typically have over equivalent instrumented tests run on an actual emulator/device?
Questions in this quiz
What is a reasonable justification for the significant SPEED advantage Robolectric-based tests typically have over equivalent instrumented tests run on an actual emulator/device?
What is `Robolectric.buildActivity()` (or a similar activity-controller API) used for in a Robolectric test, and what does it let a test do with an Activity's lifecycle?
What is a reasonable justification for Robolectric being particularly valuable specifically for testing Android `Fragment` classes, given Fragments' own somewhat complex lifecycle and dependency on being hosted within an Activity?
What is a reasonable way Robolectric's ability to run WITHOUT an emulator specifically benefits a developer's LOCAL, day-to-day development workflow (as opposed to CI infrastructure specifically)?
What is a reasonable justification for a team incorporating Robolectric-based tests into their Continuous Integration (CI) pipeline, particularly given the speed characteristics discussed earlier?
What is the purpose of the `@Config` annotation in Robolectric, e.g. `@Config(sdk = [33])`?
What is Robolectric?
What is a reasonable justification for a team choosing to write Robolectric-based tests specifically for testing an Android `ViewModel` or business logic class that interacts with Android framework classes (like `Context`), rather than avoiding that interaction entirely just to enable simpler, framework-free JVM unit testing?
What is a reasonable comparison between Robolectric and a purely MOCKING-based approach (using a library like Mockito to mock out Android framework classes entirely) for testing Android-dependent code?
What problem does Robolectric solve regarding the traditional distinction between Android "unit tests" (running on the JVM) and "instrumented tests" (requiring an actual device/emulator)?
What is a reasonable way a large, long-established Android codebase might gradually adopt Robolectric for an EXISTING suite of slow instrumented tests, rather than needing to rewrite the entire test suite at once?
What is a reasonable justification for a team using Robolectric specifically to test how their app handles a `SharedPreferences`-based feature (Android's simple key-value local storage mechanism), rather than mocking out SharedPreferences entirely?