You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
1 year ago | |
|---|---|---|
| .. | ||
| README.md | 1 year ago | |
| android_test_instructions.md | 1 year ago | |
| components_for_testing.md | 1 year ago | |
| gtest_implementation.md | 1 year ago | |
| instrumentation.md | 1 year ago | |
| junit.md | 1 year ago | |
| junit4.md | 1 year ago | |
| todo.md | 1 year ago | |
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.
- 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
How do I...
- set up
- writing tests
- running tests
- debugging tests
- miscellaneous