Google Testing Blog: Android Platform Testing Made Easy

Android Platform Testing Made Easy

Tuesday, January 15, 2019

Android Compatibility Test SuiteTrade Federation Test HarnessSoong build systemTest MappingAtest Configuring tests in Soong buildsSoong build systemAndroid.mksimple build configurationandroid_testAndroid.bp/platform_testing/tests/example/instrumentation/Android.bp

android_test {

name: "HelloWorldTests",

srcs: ["src/**/*.java"],

sdk_version: "current",

static_libs: ["android-support-test"],

certificate: "platform",

test_suites: ["device-tests"],

}

android_testandroid_appComplex test configuration Mapping tests in the source treeTest MappingTEST_MAPPINGtest grouppresubmitpostsubmitTEST_MAPPINGTEST_MAPPING{ "presubmit": [ { "name": "CtsAccessibilityServiceTestCases", "options": [ { "include-annotation": "android.platform.test.annotations.Presubmit" } ] } ], "postsubmit": [ { "name": "CtsWindowManagerDeviceTestCases" } ], "imports": [ { "path": "frameworks/base/services/core/java/com/android/server/am" } ]} Running tests locally with AtestAtestTrade Federation Test Harness
atest [optional-arguments] test-to-run
atest test-to-run-1 test-to-run-2
LOCAL_MODULELOCAL_PACKAGE_NAMEAndroid.mkAndroid.bp
For example:atest FrameworksServicesTests
atest CtsJankDeviceTestCases Discovering tests with Atest and TEST MAPPING

Go to the directory containing the TEST_MAPPING file.

Run the command: atest

All presubmit tests configured in the TEST_MAPPING files of the current directory and its parent directories are run. Atest will locate and run two tests for presubmit. Finding more testing documentationsource.android.com

Android Platform Testing

Test Development Workflow

Simple Test Configuration

Instrumentation Tests

Native Tests

JAR (Java) Host Tests

ci.android.comMore visibility into the Android Open Source ProjectContinuous Integration Dashboard
Google Testing BlogAndroid Developers Blogsource.android.com