Merge tag 'android-13.0.0_r52' into int/13/fp3

Android 13.0.0 Release 52 (TQ3A.230605.012)

* tag 'android-13.0.0_r52':
  Adds the ability to set the font scale via Config.
  Merge branch 'upstream-google' into third_upstream_to_master
  Add support for ARSC resource table compact encoding
  Add packages/apps/Car/libs visibility to Robolectric_all-target_upstream
  Add packages/apps/Car/libs missing visibility to fix the build.
  Add robolectric services providers to the config
  Restrict robolectric usage to existing modules, per agreement with framework.
  Restrict robolectric usage to existing modules, per agreement with framework
  Add robolectric services providers to the config
  Fix issue with native fonts dir. Test: atest -c MyRoboTests Bug:  263483214
  Merge branch 'upstream-google' into rng7 Bug: 263483214 Test: atest -c MyRoboTests

Change-Id: I38e5d031541e1c1c2a271f747ccc0765fa4cd73f
tree: 2aba65167e81ebf211f1503a64fa3f5ccc08c537
  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. Android.bp
  25. build.gradle
  26. CODE_OF_CONDUCT.md
  27. dependencies.gradle
  28. gradle.properties
  29. gradlew
  30. gradlew.bat
  31. LICENSE
  32. MODULE_LICENSE_MIT
  33. NOTICE
  34. OWNERS
  35. README.md
  36. settings.gradle
  37. 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 and flakiness of an emulator. Robolectric tests routinely run 10x faster than those on cold-started emulators.

Robolectric supports running unit tests for 17 different versions of Android, ranging from Jelly Bean (API level 16) to TIRAMISU (API level 33).

Usage

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.

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 "junit:junit:4.13.2"
testImplementation "org.robolectric:robolectric:4.10-alpha-1"

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.

Prerequisites

Those software configurations are recommended and tested.

  • JDK 11. Gradle JVM should be set to Java 11.
    • For command line, make sure the environment variable 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.
    • For both IntelliJ and Android Studio, see Settings/Preferences | Build, Execution, Deployment | Build Tools | Gradle.

See Building Robolectric for more details about setting up a build environment for Robolectric.

Building

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

Testing

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

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.10-SNAPSHOT"
}