Settings is a platform app so the role APIs for it wasn't system APIs, but just @hide. Now that we are moving role into module, we need to create system APIs for them. RoleControllerManager is an implementation detail and may change in soon when we move role logic into system server and leave only UI in PermissionController, so we shouldn't expose it. Instead, we can expose the new system APIs on RoleManager, and delegate to RoleControllerManager internally. Bug: 158736025 Test: presubmit Test: atest DefaultSmsShortcutPreferenceControllerTest Change-Id: Iafe1d24601a32799e04d9aa385ec2fbce833a02e
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.