| commit | b389034f9a2ff9adfcfe8dbddb54f60ca23cc9ca | [log] [tgz] |
|---|---|---|
| author | hoisie <hoisie@google.com> | Tue Nov 24 15:39:03 2020 -0800 |
| committer | Michael Hoisie <hoisie@google.com> | Mon Dec 14 14:38:21 2020 -0800 |
| tree | e110c7a28c9e673fb94b13754b08d03dbd4b3728 | |
| parent | 511f3fe03d988fba7b1d6e850e76c7a59f99723e [diff] |
Stop bundling Robolectric Processor's sdks.txt file as a Java resource The resources approach would be difficult to get working in Gradle/Maven for custom shadow packages outside of the Robolectric project itself. This is because in Gradle/Maven, the the processor jar file currently contains a sdks.txt resource that has hardcoded paths from the releaser's workstation. Instead switch to a file-based scheme and emit the sdks.txt file to Robolectric's root project's build directory. With a file based scheme is is possible for external projects to specify an sdks.txt file path as well. Also turn off the ImplementsValidator plugin off by default as it is non-trivial for custom shadow packages in the Gradle/Maven world to generate sdks.txt files. This validation is primarily intended for the Robolectric project itself. Fixes #4801 PiperOrigin-RevId: 344144378
- processor/build.gradle[diff]
- processor/src/main/java/org/robolectric/annotation/processing/RobolectricProcessor.java[diff]
- processor/src/main/java/org/robolectric/annotation/processing/validator/SdkStore.java[diff]
- .circleci/
- .github/
- annotations/
- buildSrc/
- errorprone/
- gradle/
- images/
- integration_tests/
- junit/
- pluginapi/
- plugins/
- processor/
- resources/
- robolectric/
- sandbox/
- scripts/
- shadowapi/
- shadows/
- testapp/
- utils/
- .gitignore
- build.gradle
- CODE_OF_CONDUCT.md
- gradle.properties
- gradlew
- gradlew.bat
- LICENSE
- README.md
- resources.arsc
- settings.gradle
- WORKSPACE
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.4"
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.5-SNAPSHOT" }