On low-performance devices, this test case will activate LOW_POWER_STANDBY mode during the test, which should not be initiated in this test case.
The LOW_POWER_STANDBY mode blocks APK from accessing the network, resulting in test failures.
BUG:301027368
Signed-off-by: Wenbin.Chen <wenbin.chen@amlogic.com>
Change-Id: I1085addd22f4f3b709e1875049633832c5dac852
Test: CtsHostsideNetworkTests#com.android.cts.net.HostsideRestrictBackgroundNetworkTests
Wenbin.Chenauthored and chen wenbincommited 2023-11-15 02:48:09 +00:00
Wait for all broadcasts to be dispatched before we verify apps
network blocked status has changed.
Bug: 275459047
Test: atest --rerun-until-failure 50 ./tests/cts/hostside/src/com/android/cts/net/HostsideNetworkPolicyManagerTests.java
Ignore-AOSP-First: wait-for-broadcast-barrier is not available in AOSP
Change-Id: I27f1fcd0b80d8f9a6afd05393d5fc8ce71c6b2d4
Bug: 177641226
Test: atest ./tests/cts/hostside/src/com/android/cts/net/HostsideRestrictBackgroundNetworkTests.java
Ignore-AOSP-First: Expedited jobs are not available in AOSP
Change-Id: Ic75ebdc184764b7e7ac02d3e2ca18cbba1c55ee5
When location is disabled, Wi-Fi scan results and SSID are not available
to apps.
Fixes: 153850762
Fixes: 153396893
Test: atest hostsidetests/net/src/com/android/cts/net/HostsideRestrictBackgroundNetworkTests.java
Change-Id: I05285811d7131e116d5e1d072137ed2cf9576d05
The periodic parole window is the 10 minute window that occurs every
24 hours to let RARE apps run. Now that we have the quota system in
place, there's no need to have the periodic parole window. Alarms and
jobs will still be allowed to run when charging. Network will continue
to be restricted for RARE apps even when charging. JobScheduler requests
an exception for RARE jobs in quota, so they will still be able to run.
With this change, idle apps should still not get network when charging
unless JobScheduler requests it, so we have to update the tests.
Bug: 136184981
Test: atest AppStandbyControllerTests
Test: atest CtsAlarmManagerTestCases
Test: atest com.android.cts.net.HostsideRestrictBackgroundNetworkTests
Test: atest com.android.server.AlarmManagerServiceTest
Test: atest com.android.server.AppStateTrackerTest
Test: atest com.android.server.job.controllers.QuotaControllerTest
Change-Id: Icd7b6eff8777f9b53a10eca521b73988f58f2d84
+ Convert tests to use Junit4
+ Add annotations to specify required conditions for the test to run.
Bug: 137859686
Test: atest hostsidetests/net/src/com/android/cts/net/HostsideRestrictBackgroundNetworkTests.java
Test: atest hostsidetests/net/src/com/android/cts/net/HostsideNetworkCallbackTests.java
Change-Id: I93317c201a0ea06732e29154ab7e140735381f59
This will allow running this module against a secondary
user in continuous infra to uncover bugs.
Test: run cts-unit-tests
Bug: 130892086
Change-Id: Ic8af2e3e77e24db340b2894c2d36e3501962952c
These are not multi-ABI because the behaviour does not depend on
the ABI of the app. Some of the APIs are ultimately backed by JNI
code in the system server, but that only depends on the system
server's ABI, not the app's.
Enable instant mode because these applications are subject to the
same network restrictions as other apps.
Fix: 123364589
Test: atest CtsHostsideNetworkTests
Test: cts-tradefed run commandAndExit cts --enable-parameterized-modules --module-parameter instant_app -m CtsHostsideNetworkTests
Change-Id: Ib3c4cd365ffe95889d51a236f035ea84516f0abd
Lorenzo Colitticommited 2019-04-11 20:43:59 +09:00
Resetting battery status makes the "disabling battery saver mode"
operation that follows it a no-op if the device is plugged-in to power.
In this case, sticky battery saver status won't get reset and might
affect the tests following it.
Also, change back turnBatteryOff -> "cmd battery reset" since issue "72502904"
is fixed now.
Fixes: 77236363
Test: cts-tradefed run singleCommand cts-dev -m CtsHostsideNetworkTests -t \
com.android.cts.net.HostsideRestrictBackgroundNetworkTests
Change-Id: I93e11c714200e8de6864a3bd7627eb66842a39d1
Some of the tests in CtsHostsideNetworkTests module will put the
test app in App standby mode and check the network availability.
If the device enters into parole state during the test, then the test
fails. Set the parole_duration to 0 so that it won't parole state
won't affect these tests.
Bug: 63140218
Test: cts-tradefed run singleCommand cts-dev -m CtsHostsideNetworkTests -t \
com.android.cts.net.HostsideRestrictBackgroundNetworkTests
Change-Id: I8158eba74f03e82566de1de9f94b981b17175df5
Wenbin.Chen
authored and
Chiachang Wang
authored and
Automerger Merge Worker
commited 
Sudheer Shanka
commited 
Kweku Adams
commited 
Julien Desprez
commited 
Lorenzo Colitti
commited 
Guang Zhu
commited 
Nicholas Sauer
commited 
Nash Lincoln
commited