Clone this repo:
  1. ca6067e Merge "Add android-all-robolectric.jar to private_api_stubs" into main by Treehugger Robot · 10 hours ago main master
  2. c26a513 Add android-all-robolectric.jar to private_api_stubs by Peter Kalauskas · 16 hours ago
  3. 5f581e6 Merge "Moves Robolectric fonts back to Robolectric." into main by Ang Li · 6 days ago
  4. ec14fea Moves Robolectric fonts back to Robolectric. by Ang Li · 7 days ago
  5. 9e8ce31 Merge "Temporarily disable SQLiteDatabaseTest from ctesque tests" into main by Kevin Liu · 8 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 15 different versions of Android, ranging from KitKat (API level 19) to U (API level 34).


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.11.1"

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.


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.12-SNAPSHOT"