Files

Thomas Devaux 158d17fef6 Auto-open Captive Portal when user clicks on open network.

Rationale: many users are confused about what to do after tapping the captive
portal network in Settings, and since there is explicit user action to
connect to that network at that point, auto-opening the portal is
natural and makes it simpler.

Bug: 148538768
Test: manually with local AP with Captive Portal and:
> make RunSettingsRoboTests -j40
> atest com.android.server.ConnectivityServiceTest

Change-Id: I29573132cd3e46ff22e6f67bb3678516fabac47d

2020-02-12 00:45:46 +00:00

assets

Revert "Settings search - Navigate user to exact page"

2020-01-16 14:07:38 +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

Auto-open Captive Portal when user clicks on open network.

2020-02-12 00:45:46 +00: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.