Google Git
Sign in
android / platform / external / robolectric-shadows / 31c4a3ac40b03a14ce79daa19667c3e100dc843e
commit31c4a3ac40b03a14ce79daa19667c3e100dc843e[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Tue Jun 19 15:55:05 2018 -0700
committerDan Willemsen <dwillemsen@google.com>Tue Jun 19 16:23:05 2018 -0700
tree4c32a601d8c1f4564a2ca5d64ddd40137b43e4b4
parent701d053c14db47c9f83844f148ce4e8da58bc3d2 [diff]
Stop declaring real files as phony

I've added some logic into Kati to attempt to prevent this type of
thing, since in the majority of cases, we expected a command to only run
if one of its dependencies has changed.

Workaround this specific case by declaring an output that is never
written. DO NOT use this elsewhere without permission. There will
eventually be a check for this workaround as well, but by that time
we'll probably be ready to mark rules that should not be cached.

Test: m RunSettingsLibRoboTests; m RunSettingsLibRoboTests
Test: m Run_robolectric_utils_tests; m Run_robolectric_utils_tests
Change-Id: Ifa9be1b299c0188b9e5f5886a4c80a21de42b0a1
2 files changed
tree: 4c32a601d8c1f4564a2ca5d64ddd40137b43e4b4
  1. .github/
  2. annotations/
  3. buildSrc/
  4. gradle/
  5. images/
  6. integration_tests/
  7. junit/
  8. processor/
  9. resources/
  10. robolectric/
  11. sandbox/
  12. scripts/
  13. shadowapi/
  14. shadows/
  15. src/
  16. utils/
  17. .gitignore
  18. .travis.yml
  19. Android.mk
  20. build.gradle
  21. circle.yml
  22. CODE_OF_CONDUCT.md
  23. gradle.properties
  24. gradlew
  25. gradlew.bat
  26. java-timeout
  27. LICENSE
  28. list_failed.sh
  29. MODULE_LICENSE_MIT
  30. NOTICE
  31. README.md
  32. report-internal.mk
  33. robotest-internal.mk
  34. robotest.sh
  35. run_robolectric_module_tests.mk
  36. run_robotests.mk
  37. settings.gradle
  38. wrapper.sh
  39. wrapper_test.sh
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.6.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.7-SNAPSHOT"
}