commit | d9fc79d39485bc3082d7464a6d89cf4feec78f4e | [log] [tgz] |
---|---|---|
author | Paul Sowden <paulsowden@google.com> | Fri Oct 07 23:09:20 2022 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 07 23:09:57 2022 -0700 |
tree | bb2bc1786cd0f392456be598624226dcc5ff4036 | |
parent | de5ac71859c8e596ce98b7b655caf8b8a7a11104 [diff] |
Fix configuration/resource handling in activity contexts A few fixes to address correct behavior of configuration and resources when using activity contexts: * Create the activity token before creating the activity context and correctly pass it in instead of passing in the null token from the base context, this is necessary as the context uses the token to key resources so using a null token results in activities using incorrect asset managers * Pass through a correct override config when creating the activity context, most of the time the override config can safely be null and just inherit from the application but when explicitly configuring resources on an activity during configuration change we should pass in the request override * Trigger activity configuration change for `ActivityScenario` (i.e. those created by the instrumentation) activities based on the application resources changing configuration rather than the static system ones, applications generally expect the application configuration to be consistent with the activity resources and `RuntimeEnvironment` is configuring the application resource configurations after the system ones so triggering on the system ones was too early. PiperOrigin-RevId: 479738327
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 16 different versions of Android, ranging from Jelly Bean (API level 16) to SV2 (API level 32).
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.8.2"
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
.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.9-SNAPSHOT" }