Clone this repo:
  1. 6c95e18 Bump com.googlecode.libphonenumber:libphonenumber by dependabot[bot] · 33 hours ago master
  2. ceb8184 Increase duration of awaitFinalized to 15s from 10s by utzcoz · 34 hours ago
  3. 143c20e Auto close ActivityController for ShadowThemeTest by utzcoz · 34 hours ago
  4. c6a97d6 Double duration of awaitFinalized in ShadowThemeTest by utzcoz · 36 hours ago
  5. 79def76 Bump error-prone from 2.21.1 to 2.22.0 by dependabot[bot] · 2 days ago

Build Status GitHub release

Robolectric is the industry-standard unit testing framework for Android. With Robolectric, your tests run in a simulated Android environment inside a JVM, without the overhead and flakiness of an emulator. Robolectric tests routinely run 10x faster than those on cold-started emulators.

Robolectric supports running unit tests for 17 different versions of Android, ranging from Jelly Bean (API level 16) to TIRAMISU (API level 33).


Here's an example of a simple test written using Robolectric:

public class MyActivityTest {

  public void clickingButton_shouldChangeResultsViewText() {
    Activity activity = Robolectric.setupActivity(MyActivity.class);

    Button button = (Button) activity.findViewById(;
    TextView results = (TextView) activity.findViewById(;

    assertThat(results.getText().toString(), equalTo("Testing Android Rocks!"));

For more information about how to install and use Robolectric on your project, extend its functionality, and join the community of contributors, please visit


Starting a New Project

If you'd like to start a new project with Robolectric tests you can refer to deckard (for either maven or gradle) as a guide to setting up both Android and Robolectric on your machine.


testImplementation "junit:junit:4.13.2"
testImplementation "org.robolectric:robolectric:4.10.3"

Building And Contributing

Robolectric is built using Gradle. Both IntelliJ and Android Studio can import the top-level build.gradle file and will automatically generate their project files from it.


Those software configurations are recommended and tested.

  • JDK 17. Gradle JVM should be set to Java 17.
    • For command line, make sure the environment variable JAVA_HOME is correctly point to JDK17, or set the build environment by Gradle CLI option"YourJdkHomePath" or by Gradle Properties
    • For both IntelliJ and Android Studio, see Settings/Preferences | Build, Execution, Deployment | Build Tools | Gradle.

See Building Robolectric for more details about setting up a build environment for Robolectric.


Robolectric supports running tests against multiple Android API levels. The work it must do to support each API level is slightly different, so its shadows are built separately for each. To build shadows for every API version, run:

./gradlew clean assemble testClasses --parallel


Run tests for all API levels:

The fully tests could consume more than 16G memory(total of physical and virtual memory).

./gradlew test --parallel

Run tests for part of supported API levels, e.g. run tests for API level 26, 27, 28:

./gradlew test --parallel -Drobolectric.enabledSdks=26,27,28

Run compatibility test suites on opening Emulator:

./gradlew connectedCheck

Using Snapshots

If you would like to live on the bleeding edge, you can try running against a snapshot build. Keep in mind that snapshots represent the most recent changes on master and may contain bugs.


repositories {
    maven { url "" }
dependencies {
    testImplementation "org.robolectric:robolectric:4.11-SNAPSHOT"