Google Git
Sign in
android / platform / external / robolectric / 0f1c9be53
commit0f1c9be539cd0fd23383a92a9fe7f28b8e267c27[log] [tgz]
authorhoisie <hoisie@google.com>Tue Nov 16 23:09:29 2021 -0800
committerMichael Hoisie <hoisie@google.com>Wed Nov 17 15:20:10 2021 -0500
treeb83ea1b3eb1e06bdb1c6f573af3c892e9b5963d6
parent326991f87357af49c8eb10d6a4995a8b95918368 [diff]
Limit instrumentation on interfaces

Previously, Robolectric enabled some of its instrumentation on interfaces
in order to support hooking up interceptors on default interface methods.
This is because there are now some default interface methods that invoke
System.logW (e.g. android.compat.Compatibility$BehaviorChangeDelegate)

However, the instrumentation step that makes classes public
was also applied to interfaces, and this seems to confuse Mockito/ByteBuddy,
but only in certain environments.

As a fix, restrict the instrumentation to only rewrite interface method
bodies, as well as extends 'InstrumentedInterface', so Robolectric does
not re-instrument interfaces when the preinstrumented jars are used.

A test case will be added after the preinstrumented jar version is
bumped.

Fixes #6858

PiperOrigin-RevId: 410440888
1 file changed
tree: b83ea1b3eb1e06bdb1c6f573af3c892e9b5963d6
  1. .github/
  2. annotations/
  3. buildSrc/
  4. errorprone/
  5. gradle/
  6. images/
  7. integration_tests/
  8. junit/
  9. nativeruntime/
  10. pluginapi/
  11. plugins/
  12. preinstrumented/
  13. processor/
  14. resources/
  15. robolectric/
  16. sandbox/
  17. scripts/
  18. shadowapi/
  19. shadows/
  20. testapp/
  21. utils/
  22. .gitignore
  23. .gitmodules
  24. build.gradle
  25. CODE_OF_CONDUCT.md
  26. gradle.properties
  27. gradlew
  28. gradlew.bat
  29. LICENSE
  30. README.md
  31. settings.gradle
  32. WORKSPACE
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(AndroidJUnit4.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:

testImplementation "org.robolectric:robolectric:4.7"

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 testClasses --parallel

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 {
    testImplementation "org.robolectric:robolectric:4.8-SNAPSHOT"
}