Files

Eran Messeri d8e49b45b1 Enforce password complexity in lockscreen setting

Enforce a lock screen that adheres with the required complexity set by
the admin.

This is done by querying the DevicePolicyManager for the complexity set
for the given user, and merging it with the complexity from the "change
lock screen" intent (if any).

If the admin sets a higher complexity requirement than the app
triggering the lock screen change request, then the admin-set complexity
is enforced and the user is not shown information about the requesting
app.

Bug: 165573442
Test: Manually, set complexity using TestDPC and see it applies.
Test: m RunSettingsRoboTests ROBOTEST_FILTER=com.android.settings.password.ChooseLockGenericTest
Test: m RunSettingsRoboTests ROBOTEST_FILTER=com.android.settings.password.ChooseLockPasswordTest
Change-Id: If3f24f7430bdcbcd34265339f7d2a1ff82a44fc1

2020-11-30 22:26:50 +00:00

assets

Add a setting page for Reduce Bright Colors under A11y

2020-10-21 23:08:53 +00:00

config

…

res

Update language to comply with Android's inclusive language guidance

2020-08-12 11:29:07 +08:00

resources/META-INF/services

…

src/com/android/settings

Enforce password complexity in lockscreen setting

2020-11-30 22:26:50 +00:00

Android.bp

Add explicit dep on framework-wifi.impl

2020-09-02 15:41:40 +00:00

AndroidManifest.xml

…

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.