AssertionFailedError is a Throwable and hence some logs which will
help debug the failures are not printed.
Bug: 38384021
Test: Verified that when the test throws AssertionFailedError, required
logs are printed.
Change-Id: I6cc8e0172b8e30d268a50bdf9281d6828fc74810
- Add some logging to dump usage stats if setting an app as inactive
fails.
Bug: 38384021
Test: cts-tradefed run singleCommand cts-dev -m CtsHostsideNetworkTests -t \
com.android.cts.net.HostsideRestrictBackgroundNetworkTests
Change-Id: I96d7acabcf3dc18b4187775bbd2bce17a49dbb7b
Bug: 36140955
Bug: 35360169
Test: new unit test to ensure that all modules have this field
Change-Id: Ie76e4306049eb56e7f4360f63093ab03b3ca2611
Merged-In: Id856f93c0d2a018be65bff33459b4b703d23257d
- use the new tradefed version of it.
- add a tests to check configs.
Test: build, run collect-tests-only dry-run
Bug: 37213493
Change-Id: I45e9950aa2731afe9403dd44dd18d0a8d40fdb6b
Merged-In: Ia212b707befe3ffc70ef43cbc292e97be3f364f1
- If the screen is not turned on when the activity is starting, then
that process will be in TOP_SLEEPING state and won't have temp access
to network connectivity in restricted modes. So, add a wait time after
turning the screen on.
- Increase the timeout for app standby wait time.
Bug: 38384021
Test: cts-tradefed run singleCommand cts-dev -m CtsHostsideNetworkTests -t \
com.android.cts.net.HostsideRestrictBackgroundNetworkTests
Change-Id: I54563a0c8b3e783ee9279d667faa5cab529ddc7e
Add new CTS tests for the LocalOnlyHotspot feature. This CL also
creates a reusable method for confirming that wifi is enabled via the
setWifiEnabled call. This should reduce flake in automated test runs by
setting local variables before wifi is enabled instead of after the
call. This change removes a race condition on confirming if wifi is
enabled.
Bug: 31466854
Test: ran new CTS tests
Test: no new failures with 'run cts-dev --module CtsNetTestCases -t ran n
android.net.wifi.cts.WifiManagerTest'
Change-Id: Id119170fea742402dda10d83014d27b8dbc98e92
The current assertion in the test is incorrect. When we disable wifi,
we should expect scans to pass if location scans are turned on, else
scans should fail.
Also, reset mScanResults in startScan so that it doesn't contain stale
scan results.
Bug: 38224452
Test: Run the cts test with both location scan turned on & off.
`cts-tradefed run cts-dev --module CtsNetTestCases -t
android.net.wifi.cts.WifiManagerTest#testWifiManagerActions`
Change-Id: I27bc88ca4883d9233da9e911397192a1eef4422b
WifiManager#pingSupplicant is deprecated and its semantics had changed.
So remove it in testWifiManagerActions to fix the test.
Bug: 37991667
Test: cts-tradefed run cts-dev --module CtsNetTestCases --test
android.net.wifi.cts.WifiManagerTest#testWifiManagerActions
Change-Id: I9b64cb6d03c253f143a78caca72b75678973034b
The APIs for Release 2 configuration are now hidden,
so remove the usage of those APIs.
Also use a trusted public certificate instead of a fake
one for testing Release 1 configuration, since it will
be verified by WifiService when adding a Release 1 configuration.
Bug: 37907977
Test: cts-tradefed run cts-dev --module CtsNetTestCases --test android.net.wifi.cts
Change-Id: Ie1056b97da1597ff1cdc979e9c2a57f19f58e0a3
The changes made to ensuring network connectivity on app start
only applies to activities. There is no change in how the services
are handled.
Bug: 27803922
Test: cts-tradefed run singleCommand cts-dev -m CtsHostsideNetworkTests -t \
com.android.cts.net.HostsideRestrictBackgroundNetworkTests
Change-Id: Ib82b07195e395c89701dd525b850c0935d94dfe7
IpSecManager and its associated classes are removed from OC.
They are planned for a future release.
Bug: 37681043
Test: make cts
Change-Id: I2ff911d5c62dbbf9be699330742d041706d9cbc2
Merged-In: I2ff911d5c62dbbf9be699330742d041706d9cbc2
(cherry picked from commit 3a51173a3a762b576dd3c0d29c883e8763a9f95b)
Aware classes with destroy() methods (containing resources)
converted to be AutoCloseable. As such the destroy method
was renamed.
Bug: 37514387
Test: unit tests and integration (sl4a) tests passing.
Merged-In: I433d7cf6f4c60bab4230702075ea22b9c56f31af
Change-Id: I433d7cf6f4c60bab4230702075ea22b9c56f31af
Because the DatagramSocket version of the API is being
hidden, this test is being converted to use the
FileDescriptor version of applyTransportModeTransform()
and removeTransportModeTransform()
Bug: 37446006
Test: compilation
Merged-In: Ida4977a6e7496ce6b4de38bfd48bd6a162cab874
Change-Id: Ida4977a6e7496ce6b4de38bfd48bd6a162cab874
(cherry picked from commit 8e0db4ceaa9b2940942132e452d44cd59ff971e2)
Add two new test cases to ConnectivityManagerTest:
testRouterSolicitations()
testRouterSolicitationMaxInterval()
Bug: 33620395
Test: ConnectivityManagerTest CTS test passes with WIFI on/off
Change-Id: Iac8979dfab29ae75343a355d02acfb0f39b491f9
Add two new test cases to ConnectivityManagerTest:
testAcceptRaRtInfoMinPlen()
testAcceptRaRtInfoMaxPlen()
Bug: 33333670
Test: ConnectivityManagerTest CTS test passes with WIFI on/off
Change-Id: I3c0a6823b6fa75f55f9bb99b59557abeb5b9ac62
This is a minor code health change motivated by upcoming additions to
ConnectivityManagerTest. Common code to drive WIFI to a connected state
is now shared along with automatic cleanup code to restore wifi to its
original state in tearDown().
Bug: 33333670
Test: CtsNetTestCases test passes
Change-Id: I62a2748f113650f7a235af3074e33cc0cefe4a3b
(cherry picked from commit 49eaabd72c1a5346750342ffc956c4b903ca532c)
For devices with build config |config_wifi_hotspot2_enabled| set to false
(Passpoint disabled), an UnsupportedOperationException will be thrown
when Passpoint related WifiManager APIs are invoked. For these devices,
the testing of Passpoint APIs are not relevant. So just catch and ignore
this type of exceptions to avoid any test failures.
While there, set the UpdateIdentifier for Passpoint configurations, to avoid
the CA certificate verification when adding the config, since we're using
a fake CA certificate for testing.
Bug: 36863137
Test: cts-tradefed run cts-dev -m CtsNetTestCases -t android.net.wifi.cts.WifiManagerTest
Change-Id: I8ebdc58349c33f13b510c3d9e2a5fc8ce4ef09c4
-Test SPI creation, duplication and deletion
-Test IpSecTransform creation, apply to socket, and delete
Bug: 30984788, 34811227
Test: Verified on Bullhead with UDP on IPv6 (default)
Change-Id: I1ffc84e549c7666996472ed323eb44810c3b9843
(cherry picked from commit 4eddc41200c1912b40218d0ee7b0f0cc05c1a960)
Add time-to-live (TTL) testing on publish/subscribe. Can
be verified with single device testing.
Bug: 30556108
Test: CTS tests pass
Change-Id: Ic0fc6b7bd2bc12a5e615b3334a5373da73ccfbf6
The tests were skipped for historical reasons that are no longer
valid, and creates a hole in testing because there are now
several VPN apps that work on TVs.
Test: HostsideVpnTests passes on fugu with UID routing kernel bug fixed
Bug: 36465489
Change-Id: Ib0d6a5cec085e1fc09cf0609b08ca897629afe0c
Symptom: It should be more reasonable to use setBatterySaverMode API to leave power-save mode instead of plugging in charger for "CtsHostsideNetworkTests" test case.
Root Cause: It uses setBatterySaverMode API to enter power-save mode and uses plugging in charger to leave power save mode.It should be more reasonable to use setBatterySaverMode API to leave power-save mode instead of plugging in charger.
Solution: To use setBatterySaverMode API to leave power-save mode instead of plugging in charger.
Project: N70
Note: NA
Test done by RD:
Futher testing need Q team's support:
Change-Id: I491c5d0675f340e1c9911b84e41f034663b1454d
