Clone this repo:
  1. 4764281 Merge pull request #5680 from robolectric/piper_311487225 by brettchabot · 3 days ago master
  2. 90ca6c0 Add matcher for expected logs with exception by Googler · 6 days ago
  3. 4dc902b Merge pull request #5667 from robolectric/piper_312558186 by brettchabot · 6 days ago
  4. 75a91d0 Merge branch 'master' into piper_312558186 by brettchabot · 6 days ago
  5. e3f98fa Merge pull request #5674 from robolectric/piper_313653172 by brettchabot · 6 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 of an emulator.


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

public class MyActivityTest {

  public void clickingButton_shouldChangeResultsViewText() throws Exception {
    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 "org.robolectric:robolectric:4.3.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.

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 install compileTest

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