Merge pull request #2361 from ngbravo/remove-put-RoboAttributeSet

RoboAttributeSet API changes
tree: a199dae9aa5c3b8f96c88d93e46820b17ec5c322
  1. .gitignore
  2. .travis.yml
  4. LICENSE.txt
  6. images/
  7. pom.xml
  8. robolectric-annotations/
  9. robolectric-processor/
  10. robolectric-resources/
  11. robolectric-shadows/
  12. robolectric-utils/
  13. robolectric/
  14. scripts/

Build Status

Robolectric is a testing framework that de-fangs the Android SDK so you can test-drive the development of your Android app.


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

@Config(constants = BuildConfig.class)
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 you can use deckard (for either maven or gradle). These project will guide you through setting up both Android and Robolectric on your machine.


testCompile "org.robolectric:robolectric:3.0"



Building And Contributing

Robolectric is built using Maven. Both Eclipse (with the M2Eclipse plug-in) and IntelliJ can import the pom.xml 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 repo in order to build Robolectric.

Mavenize all required dependencies by running:


Because Robolectric's shadows are compiled against the Android APIs that they target, you must build the shadows for all API levels before being able to run any of the tests. You can build all of Robolectric by running:


After doing this once, you can build and test against the specific API level you care about:

mvn install -P android-18 (for example)

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 {
    testCompile "org.robolectric:robolectric:3.1-SNAPSHOT"