Add a new CTS test to ensure that set device mobility permission is
granted to at most 1 app.
Bug: 120097108
Test: "atest WifiManagerTest" after installing app with new
permission granted
Change-Id: Ifda2163da6da9e9365c440d47031d25f92c6c375
Ensuring that app idle network whitelisting works as expected and does
not override other power saving restrictions.
Bug: 117846754
Bug: 111423978
Test: atest CtsHostsideNetworkTests
and atest NetworkPolicyManagerServiceTest
Change-Id: I09172184e2fe543d6723639e5e62ae6afd5a6087
Vpn test would destroy socket. If adb run over network, adb
socket would be killed during Vpn test. Then, test stop due to
adb disconnect.
Bug: 119382723
Test: - build pass
- run cts -m CtsHostsideNetworkTests -t com.android.cts.net.HostsideVpnTests
Change-Id: I91b4ab018a9e7fc73dcb7969e4a6520d6b27d629
Add a new test to ensure that the NETWORK_MANAGED_PROVISIONING is only
granted to the correct app.
Bug: 115980767
Test: atest WifiManagerTest
Change-Id: Ifca1fcd81e201134bbb4173c3f142cca91ed49f9
Remove/Modify tests that are invoking the deprecated API's. Use the
shell automator to toggle wifi state.
CTS tests for the replacement API surface (i.e NetworkRequest &
NetworkSuggestion) will be added later.
Bug: 115504728
Test: `atest android.net.wifi.cts.WifiManagerTest`
Change-Id: I04b3e1572ddfd31b28639185e5cf54dd70a1ae42
Due to exposing api of toSafeString, add coresponding testing
for it.
Bug: 119153962
Test: atest UriTest
Change-Id: I156b2b03ee9c1d4a05ac635b4f684c5b4dcfca08
The dependency is unnecessary as by default conscrypt
is included in the "standard libraries".
Test: build
Bug: 113148576
Change-Id: I30d68049215c61931bdd7aa5e2a0f125e6d1bf90
The only exception is automotive builds which may start local-only
hotspot at 5Ghz
Bug:115666270
Test: run cts -m CtsNetTestCases -t
android.net.wifi.cts.WifiManagerTest#testStartLocalOnlyHotspotSuccess
Change-Id: Ic3df22dab4ee93b531b92e6ed38adfa2b75880c7
Add a much more verbose message for the common failure case in which
the CTS is run without an AP which supports IEEE 802.11mc / RTT. That
may help speed up issue resolution.
Bug: 116849381
Test: atest WifiRttTest
Change-Id: I4ea3fbe17563f0087a013cbf48f7f601fec7e363
Location Wi-Fi scanning should not be turned off when the screen turns off.
Bug: 113876483
Test: Run CTS, manually toggle location Wi-Fi scanning off right after the screen
turns on and observe failure.
Test: Run CTS with location Wi-Fi scanning initially turned off and observe failure.
Test: Run CTS with location Wi-Fi scanning initially turned on and observe
success.
Change-Id: I092a3854b6365de72c2cfe38a55a0e1cedfcabd9
This access is going away for apps. Move these tests to hostside
tests to be executed by the shell domain.
Test: atest cts/hostsidetests/net/src/com/android/cts/net/ProcNetTest.java
Test: atest android.net.cts.ConnectivityManagerTest
Test: atest android.net.cts.IpSecSysctlTest
Test: atest android.net.cts.MultinetworkSysctlTest
Bug: 116053204
Change-Id: Id7e867184dd344a2d877515956e76019d627788b
Test connection->UID resolution for both UDP and TCP connections.
Bug: 9496886
Bug: 109758967
Test: atest HostsideVpnTests
Change-Id: Ic17c64df74f65d788fd3d95a25af3c5b44946881
The shell access to the proc/xt_qtaguid/ctrl file is blocked in next
android release since no apps or users should directly read/write to
those proc files anymore. This CTS test is checking some critical kernel
behavior to make sure the xt_qtaguid module have specific kernel fixes.
So if the ctrl file is not accessible, there is no way to verify those
critical fixes, we can only skipped the test. These testcases are also
added in VTS qtaguid test so we can still check the devices have those
kernel fixes.
Bug: 110906349
Test: atest CtsNativeNetTestCases
Change-Id: Iae0512bb37f8b93577a134f15affb4f2a448be18
The internal UriCodec class is being removed from libcore/ and the
associated CTS tests are being removed. This change adds equivalent
URI decoding tests to the UriTest CTS test class.
Test: make droid && make cts
Test: run cts-dev -m CtsNetTestCases -t android.net.cts.UriTest
Bug: 111055375
Change-Id: Ided15d5abf8478064d193034e84c4dbe0689c6f0
One of the preparation steps for running cts involves loading up the sim
card with the key used to sign CtsCarrierApiTestCases.apk. It
means if the same key is used for signing networkpolicy test app too,
then the app is considered as carrier privileged by the system and can't
be forced into app standby state.
Fixes: 80077890
Test: cts-tradefed run singleCommand cts-dev -m CtsHostsideNetworkTests -t \
com.android.cts.net.HostsideRestrictBackgroundNetworkTests#testDataSaverMode_disabled
Change-Id: Iaa9f4fabe83430fa42b6f67c1025db41a5e1d938
Modify the assert message to print out the # of failures and the total
number of iterations. Will help diagnose scope of test failures.
Bug: 109836816
Test: atest WifiRttTest
Change-Id: Ic4d5b6844225edbd9704694c539e31754b7a340c
Currently, DnsTest immediately executes a DNS lookup as soon as
it starts. If the device has just connected to a network - as it
might if the test framework has just enabled wifi - and IPv6
connectivity is not yet available, the test will fail with little
proof that the network doesn't have IPv6.
Fix this by waiting for IPv6 connectivity and by adding the
active LinkProperties to the failure message.
Bug: 109670546
Test: DnsTest passes on dual-stack network
Test: DnsTest fails on IPv4-only network
Change-Id: I88b8d001f08fe41af666bccf8094c67729dda9c2
BATTERY_CHARGING which triggers the parole state
will only be sent if the level is > 90.
Change-Id: I1073e473c27eb5d29744f4a967771392729b4e1a
Fixes:80534062
Test: Verified that updating the level activates the parole mode.
