app_Settings

Files

Daniel Nishi b088010d12 Add more sane multi-profile app attribution.

Due to issues w.r.t. attribution across multiple users, we originally
duplicated the previous implementation which zeroed out the sizes. This,
however, caused system bloat due to the change in how we calculate the
system size.

By attributing apps which do not exist in the primary profile to the
first user that shows up with it installed, we can avoid accidentally
attributing it to the system size.

Bug: 62623731
Test: Settings unittest & Settings robotest
Change-Id: I9514c9ecef62ea6270723f62e6bf27c69b75f180

2017-06-15 17:25:10 -07:00

src/com/android/settings

Add more sane multi-profile app attribution.

2017-06-15 17:25:10 -07:00

Android.mk

packages/apps/Settings: Add APCT tests to the device-tests suite.

2017-03-15 15:12:51 -07:00

AndroidManifest.xml

Change build targets for settings tests

2016-01-21 12:32:15 +00:00

AndroidTest.xml

Add test config to SettingsUnitTests

2017-03-22 12:07:08 -07:00

README

Change build targets for settings tests

2016-01-21 12:32:15 +00:00

README

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

The test apk then needs to be installed onto your test device via for example
$ adb install -r out/target/product/shamu/data/app/SettingsUnitTests/SettingsUnitTests.apk

To run all tests:
$ adb shell am instrument -w com.android.settings.tests.unit/android.support.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/android.support.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/android.support.test.runner.AndroidJUnitRunner

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