commit | 33b38ed97e8d5cc78f655a931c3dfaf7ca3728f5 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Thu Feb 17 23:19:50 2022 -0800 |
committer | Michael Hoisie <hoisie@gmail.com> | Tue Mar 22 09:36:46 2022 -0700 |
tree | 3b429e845e9f04840b1af0473b888ebf930cf153 | |
parent | 759f8a4654ab1e6ca1966f20bd46dcbcdf6e14a7 [diff] |
Block `UiController#loopMainThreadUntilIdle` on registered idling resources being idle. When using the paused looper collect the registered idling resources and wait for them to become idle before returning from `loopMainThreadUntilIdle`. Because Robolectric runs on the same thread as the main looper we need to continually loop the main looper until all idling resources transition to idle state. To do this we'll first drain the looper of currently scheduled tasks and then collect all of the idling resources that are not reporting idle. While this list is not empty (we need to loop as one idling resource becoming idle may cause another idling resource to become not idle, we need to observe them all idle at once) wait on the message queue to receive new messages up to the error timeout. Issue: #4807 PiperOrigin-RevId: 436334339
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 Jelly Bean (API level 16) to S (API level 31).
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.
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.7.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 JDK11, or set the build environment by Gradle CLI option -Dorg.gradle.java.home="YourJdkHomePath"
or by Gradle Properties org.gradle.java.home=YourJdkHomePath
.ninja --version
.cmake --version
.gcc --version
.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
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.8-SNAPSHOT" }