Java Other
Switch branches/tags
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.circleci Add Android P/28/9.0 to circleci build. Aug 16, 2018
.github Update ISSUE_TEMPLATE.md Sep 7, 2017
annotations New ShadowPicker strategy for switching between shadows (e.g. for Ass… Aug 2, 2018
bazel update robolectric version to 3.8 for bazel Mar 27, 2018
buildSrc Verify shadow @implementation methods against SDKs Jul 9, 2018
errorprone Don't use public API methods if they were only recently added. Jul 25, 2018
gradle/wrapper Bump to gradle 4.7. Apr 19, 2018
images Add Robolectric logo to README. Jan 7, 2015
integration_tests New ShadowPicker strategy for switching between shadows (e.g. for Ass… Aug 2, 2018
junit Defer shadow picking to the first use of the corresponding framework … Aug 6, 2018
processor Fix bug in shadow picking for inner classes. Aug 14, 2018
resources Kill cargo-culted copyrights. Jun 28, 2018
robolectric Cleanup/fix. Aug 15, 2018
sandbox Fix bug in shadow picking for inner classes. Aug 14, 2018
scripts Use androidx.test alpha4 Jul 25, 2018
shadowapi Cleanup. Aug 6, 2018
shadows Cleanup/fix. Aug 15, 2018
testapp Replace references to android.support.test with androidx.test. Jul 9, 2018
utils Switch from assertj to truth May 5, 2018
.gitignore Ignore CTS dirs for now. Jun 9, 2017
.travis.yml Configure travis for API 27 Oct 26, 2017
CODE_OF_CONDUCT.md Update CODE_OF_CONDUCT.md Feb 26, 2017
LICENSE LICENCE file cleanup. Mar 29, 2017
README.md Don't suggest changes to inner shadow classes. Jul 25, 2018
WORKSPACE move workspace file Feb 6, 2018
build.gradle Don't suggest changes to inner shadow classes. Jul 25, 2018
gradle.properties Don't suggest changes to inner shadow classes. Jul 25, 2018
gradlew upgrade gradle to 4.1 Aug 24, 2017
gradlew.bat upgrade gradle to 4.1 Aug 24, 2017
resources.arsc Read binary resources using transliterated Android C++ code (currentl… Mar 23, 2018
settings.gradle Create BugChecker for Robolectric tests which: Jun 28, 2018

README.md

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.

Usage

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

@RunWith(RobolectricTestRunner.class)
public class MyActivityTest {

  @Test
  public void clickingButton_shouldChangeResultsViewText() throws Exception {
    Activity activity = Robolectric.setupActivity(MyActivity.class);

    Button button = (Button) activity.findViewById(R.id.press_me_button);
    TextView results = (TextView) activity.findViewById(R.id.results_text_view);

    button.performClick();
    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 http://robolectric.org.

Install

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.

build.gradle:

testCompile "org.robolectric:robolectric:3.8"

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.

You will need to have portions of the Android SDK available in your local Maven artifact repository in order to build Robolectric. Copy all required Android dependencies to your local Maven repo by running:

./scripts/install-dependencies.rb

Note: You'll need Maven installed, ANDROID_HOME set and to have the SDK and Google APIs for API Level 27 downloaded to do this.

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.

build.gradle:

repositories {
    maven { url "https://oss.sonatype.org/content/repositories/snapshots" }
}

dependencies {
    testCompile "org.robolectric:robolectric:4.0-alpha-3-SNAPSHOT"
}