Chrome Release Bot (LUCI) 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
..
OWNERS 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
README.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
android_test_instructions.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
components_for_testing.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
gtest_implementation.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
instrumentation.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
junit.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
junit4.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem
todo.md 4762b62e7d Publish DEPS for 106.0.5249.13 před 1 rokem

README.md

Android Testing in Chromium

Concepts

  • Native Unit Tests: Normal Chromium unit tests based on the gtest framework. Tests for native code.
  • Java Unit Tests: JUnit tests that run on the host machine using Robolectric to emulate Android APIs.
  • Instrumentation Tests: JUnit tests that run on Android devices (or emulators).
    • Unit Instrumentation Tests: Instrumentation tests that test an individual feature. They do not require starting up ContentShell (or Chrome browser). These use BaseActivityTestRule or BlankUiTestActivityTestCase based on BaseActivityTestRule.
    • Integration Instrumentation Tests: Instrumentation tests that bring up ContentShell (or Chrome browser) to test a certain feature in the end-to-end flow. These typically use more specialized test rules such as ContentShellActivityTestRule or ChromeActivityTestRule.

How do I…

How does it work on Android?