Files
app_Settings/tests/unit
shaoweishen dba15f821f [PhysicalKeyboard] Update Setting Feature Provider for follow up usage
rename method in provider and usage, the provider is not activated now,
this change will not have impact on current feature.

Bug: 369937888
Test: atest packages/apps/Settings/tests/robotests/src/com/android/settings/inputmethod/
Flag: NONE, rename method, no effect on current feature.

Change-Id: I1bb66b106c338a8a8730bbd9163d6a921c17b9c0
2024-10-30 08:22:10 +00:00
..
2024-01-12 16:19:47 +00:00
2024-06-27 08:46:17 +00:00

The simplest way to run all SettingsUnitTests is with atest
$ atest SettingsUnitTests

A single class can also be tested with the following command
$ atest -c <YourClassName>

// The following instructions show how to run the test suite using make + adb //

To build the tests you can use the following command at the root of your android source tree
$ make -j SettingsUnitTests

The test apk then needs to be installed onto your test device. The apk's location will vary
depending on your device model and architecture. At the end of the make command's output, there
should be a line similar to the following:
"Copy: ${ANDROID_PRODUCT_OUT}/testcases/SettingsUnitTests/arm64/SettingsUnitTests.apk"
Install via the following command:
$ adb install -r ${ANDROID_PRODUCT_OUT}/testcases/SettingsUnitTests/arm64/SettingsUnitTests.apk

To run all tests:
$ adb shell am instrument -w com.android.settings.tests.unit/androidx.test.runner.AndroidJUnitRunner

To run all tests in a specific class:
$ adb shell am instrument -w -e class com.android.settings.<class> com.android.settings.tests.unit/androidx.test.runner.AndroidJUnitRunner

To run a specific test:
$ adb shell am instrument -w -e class com.android.settings.<class>#<test> com.android.settings.tests.unit/androidx.test.runner.AndroidJUnitRunner

More general information can be found at
http://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner.html