commit | 66497dceddc06c83a5e2ec01d4a4fa1a9c7db5da | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Mon Oct 30 11:39:06 2023 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 30 11:39:43 2023 -0700 |
tree | 54548f496b5e3a770f7ded902292270d24d2ea82 | |
parent | 94c6c14baecae89eef799d3ac4ecab7f17d554bf [diff] |
Introducing SensorEventBuilder to replace ShadowSensorManager.createSensorEvent() This change refactors logic to create SensorEvents into its own class and adds the ability to set a specific Sensor instance on the SensorEvent. Before this change, users could specify only the type, and a new Sensor instance would be created. Any comparisons on the generated event.sensor property would fail deep equality checks because each event was given a new Sensor instance. It was as if the newly created SensorEvent came from a new Sensor source each time. Setting the whole Sensor allows users to create a SensorEvent that truly behaves like it came from the desired Sensor. PiperOrigin-RevId: 577906129
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 and flakiness of an emulator. Robolectric tests routinely run 10x faster than those on cold-started emulators.
Robolectric supports running unit tests for 15 different versions of Android, ranging from KitKat (API level 19) to U (API level 34).
Here's an example of a simple test written using Robolectric:
@RunWith(AndroidJUnit4.class) public class MyActivityTest { @Test public void clickingButton_shouldChangeResultsViewText() { 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.
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.
testImplementation "junit:junit:4.13.2" testImplementation "org.robolectric:robolectric:4.10.3"
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.
Those software configurations are recommended and tested.
JAVA_HOME
is correctly point to JDK17, or set the build environment by Gradle CLI option -Dorg.gradle.java.home="YourJdkHomePath"
or by Gradle Properties org.gradle.java.home=YourJdkHomePath
.See Building Robolectric for more details about setting up a build environment for Robolectric.
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
Run tests for all API levels:
The fully tests could consume more than 16G memory(total of physical and virtual memory).
./gradlew test --parallel
Run tests for part of supported API levels, e.g. run tests for API level 26, 27, 28:
./gradlew test --parallel -Drobolectric.enabledSdks=26,27,28
Run compatibility test suites on opening Emulator:
./gradlew connectedCheck
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 "https://oss.sonatype.org/content/repositories/snapshots" } } dependencies { testImplementation "org.robolectric:robolectric:4.11-SNAPSHOT" }