Files

Matthew Fritze f87a1f3f41 Establish permanently unavailable settings

Distinguish between settings which are permanently unavailable on
the device, and temporarily unavailable. This enables us to restrict
which setting slices are exposed in onSliceGetDescendants.

The primary changes in this CL are renaming:
"DISABLED_UNSUPPORTED" -> "UNSUPPORTED_ON_DEVICE"
to be more clear the the setting will cannot be accessed on the device, and,
adding a new enum to encapsulate settings which are currently unavailable, but
could be enabled in the future.

Also remove UNAVAILABLE_UNKNOWN. Devs should never need this enum.

Bug: 78910582
Bug: 79245656
Test: robotests
Change-Id: I58821a6cfd6134b3b351657b6edf5f74ead00643

2018-05-09 08:36:59 -07:00

assets

Merge "Migrate ChooseAccountActivity to DashboardFragment"

2018-04-28 06:10:25 +00:00

config

Use external/robolectric-shadows/run_robotests.mk

2018-03-04 03:50:08 -08:00

res

Add keywords to Slices

2018-04-20 14:50:55 -07:00

src/com/android/settings

Establish permanently unavailable settings

2018-05-09 08:36:59 -07:00

Android.mk

Autogenerate SearchIndexableResources subclass

2018-04-03 10:26:55 -07:00

OWNERS

Misc fixes

2018-01-11 11:39:56 -08:00

README.md

Add a readme with instructions on running tests

2017-10-31 13:14:58 -07:00

README.md

Running Settings Robolectric tests

The full suite

$ croot
$ make RunSettingsRoboTests

Running a single test class

$ croot
$ make RunSettingsRoboTests ROBOTEST_FILTER=<ClassName>

For example:

make RunSettingsRoboTests ROBOTEST_FILTER=CodeInspectionTest

You can also use partial class name in ROBOTEST_FILTER. If the partial class name matches multiple file names, all of them will be executed.