Files

Zhen Zhang a990206ee7 Create preference controller for each tethering option

These controllers are responsible for persisting preference values and
managing the visibility and switch state. TetherEnabler will be
listening to changes of shared prefernce values and turn on/off
corresponding type of tethering when tethering is on at that time.

Bug: 146582865
Test: tests are created for each controller class.
Change-Id: I7e601b2bd693da59269517d2988bade7475e7f12

2020-01-06 23:55:30 -08:00

assets

Index Caption preferences page

2019-12-17 11:35:19 +08:00

config

[Settings] Enable support on testing

2019-12-03 20:06:59 +08:00

res

Add the impl for the ability to query non-public Slices

2019-11-26 17:06:15 +08:00

resources/META-INF/services

[Settings] Enable support on testing

2019-12-03 20:06:59 +08:00

src/com/android/settings

Create preference controller for each tethering option

2020-01-06 23:55:30 -08:00

Android.bp

Merge "[Settings] Enable support on testing" am: 84a2951a33 am: fd3557954f

2019-12-04 17:26:19 +00:00

AndroidManifest.xml

Convert Settings to Android.bp

2019-05-13 13:42:01 -07:00

OWNERS

…

README.md

…

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.