13e64c9c102f45aea11fa859f4e77d59b180bf5a
This is not actually a Settings test and never was, it just used Settings as a convenient delivery mechanism for system-level privileges. Tests for the Settings app should only check that the Settings app is behaving within its remit, ie. showing system server state and making the appropriate calls to set up a connection when certain UI elements are pressed. Also since the test relies heavily on off-device state it makes a lot more sense to run as a hostside test and have the same test code responsible for pushing certificates and network configs to the device instead of including manual instructions. For an end-to-end legacy VPN test see ACTS: https://android.googlesource.com/platform/tools/test/connectivity/+/master/acts/tests/google/net/LegacyVpnTest.py For an end-to-end app VPN test see CTS hostside: https://android.googlesource.com/platform/cts/+/master/hostsidetests/devicepolicy/app/DeviceAndProfileOwner/src/com/android/cts/deviceandprofileowner/AlwaysOnVpnTest.java Test: make Settings Change-Id: Ia105c3ebd2fa5064adc4422bd3d77c3abba55634 Fix: 64040865
…
Description
No description provided
Languages
Java
89.8%
Kotlin
10.2%