Files

Chaohui Wang ee7139a889 Remove injecting developer options into Settings itself

- It can improve performance because we use less injected item
- Also use RestrictedPreference instead just checking restrictions,
  so we follow policy transparency.

Note: Renamed DevelopmentSettingsDashboardActivity to
DevelopmentSettingsActivity,
because DevelopmentSettingsDashboardActivity could in disabled state
even after Settings upgrades, use a new name to prevent this issue.

Bug: 311604902
Test: manual - turn on / off Developer Options
Test: unit test
Change-Id: I17be117ae59e59410687e6d08fd5edd034d0508f

2023-11-27 05:12:13 +00:00

assets

Fix missing declared accessibility PreferenceControllers.

2023-10-02 18:00:30 +00:00

config

Setup external/robolectric for SettingsRoboTests

2023-08-17 22:33:20 +00:00

res

Remove unused SwitchBar

2023-10-25 12:17:49 +08:00

resources/META-INF/services

Fix META-INF for settings library to match robolectric

2023-08-30 02:05:44 +00:00

src/com/android/settings

Remove injecting developer options into Settings itself

2023-11-27 05:12:13 +00:00

testutils/com/android/settings/testutils

Adds Google account login during private space setup

2023-11-03 13:50:55 +00:00

Android.bp

feat(MultiFingerMultiTap): Add two-finger triple-tap shortcut on magnification dialog

2023-10-25 13:30:27 +00:00

AndroidManifest.xml

Get basic tests working with ActivityScenario and manifest

2023-10-11 20:59:41 +00:00

new_tests_hook.sh

…

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.