History

ziv-gabel 06ee9615ad Initial commit: AOSP 14 with modifications for Unplugged OS		2025-10-06 13:59:42 +00:00
..
android_test_instructions.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00
components_for_testing.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00
gtest_implementation.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00
instrumentation.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00
junit4.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00
junit.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00
README.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00
todo.md	Initial commit: AOSP 14 with modifications for Unplugged OS	2025-10-06 13:59:42 +00:00

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.

set up
- ... set up a device for local testing?
- ... set up an emulator for local testing?
writing tests
running tests
debugging tests
- ... debug junit tests?
- ... debug flaky tests?
miscellaneous
- ... use code coverage for Java tests?