tree: bfb342e3801cd588fdda142cf8b59b6100fc5227 [path history] [tgz]
  1. android_test_instructions.md
  2. components_for_testing.md
  3. gtest_implementation.md
  4. instrumentation.md
  5. junit.md
  6. junit4.md
  7. OWNERS
  8. README.md
  9. todo.md
testing/android/docs/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?