Java Other
Switch branches/tags
Latest commit bd2b6b8 Feb 21, 2018
Permalink
Failed to load latest commit information.
.github Update ISSUE_TEMPLATE.md Sep 7, 2017
annotations Refine shadow method selection algorithm. Jan 26, 2018
bazel Rename setup_robolectric.bzl to conform with other external repositor… Feb 9, 2018
buildSrc Merge branch 'master' into rawres Nov 15, 2017
gradle/wrapper Fix build error related to annotation processing. Nov 14, 2017
images Add Robolectric logo to README. Jan 7, 2015
integration_tests Re-introducing support for Espresso APIs, adding an additional Shadow… Feb 22, 2018
junit Fix JDK 9 breakage. Feb 8, 2018
processor Merge pull request #3130 from robolectric/protected-implementation-me… Jan 2, 2018
resources Add ability to instrument entire jars. Feb 14, 2018
robolectric Re-introducing support for Espresso APIs, adding an additional Shadow… Feb 22, 2018
sandbox Fix some CheckStyle warnings. Feb 3, 2018
scripts Re-introducing support for Espresso APIs, adding an additional Shadow… Feb 22, 2018
shadowapi Add ability to instrument entire jars. Feb 14, 2018
shadows Re-introducing support for Espresso APIs, adding an additional Shadow… Feb 22, 2018
testapp Migrate more tests from ShadowResourcesTest to ResourcesTest. Feb 22, 2018
utils Apply sheepfood changes missed during prior syncs. Jan 30, 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 Restore README.md changes for 3.7.1 Feb 15, 2018
WORKSPACE move workspace file Feb 6, 2018
build.gradle Re-introducing support for Espresso APIs, adding an additional Shadow… Feb 22, 2018
circle.yml Switch circleci resource class to xlarge. Oct 31, 2017
gradle.properties Bump version to 3.8-SNAPSHOT. Feb 9, 2018
gradlew upgrade gradle to 4.1 Aug 24, 2017
gradlew.bat upgrade gradle to 4.1 Aug 24, 2017
settings.gradle Create a new integration_tests module - CTesque designed to validate Feb 20, 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)
@Config(constants = BuildConfig.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.7.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.

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 23 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:3.8-SNAPSHOT"
}