Files

Tetiana Meronyk 7968047fc5 Disable multiuser toggle when more than 1 user is created

It makes more sense to have the toggle as on permanently as long as there are other users on the device. Otherwise if we toggle off "Allow multiple users", other users get hidden. Also with current behaviour the any admin can switch the toggle and this can block any other user, including main, from being able to use the device.

Bug: 295183792
Test: atest MultiUserSwitchBarControllerTest && UserSettingsTest
Change-Id: I8cb0671d780f45c17a9bb7c9a9d3b108128ead9d

2023-08-15 15:59:14 +00:00

assets

Merge changes from topic "simplify_pw" into udc-qpr-dev am: e414d40e60 am: 3f4b3fdce8

2023-07-18 02:36:44 +00:00

config

…

res

Remove PreferenceXmlParserUtils deprecated methods

2023-08-02 10:16:31 +08:00

resources/META-INF/services

…

src/com/android/settings

Disable multiuser toggle when more than 1 user is created

2023-08-15 15:59:14 +00:00

testutils/com/android/settings/testutils

Use resource processor for Settings

2023-08-11 22:39:08 +08:00

Android.bp

Use resource processor for Settings

2023-08-11 22:39:08 +08:00

AndroidManifest.xml

…

new_tests_hook.sh

Precommit hook added to Settings, preventing the creation of new Robolectric tests.

2020-12-10 14:40:49 +08: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.