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
Add a native test to check the qtaguid module nolonger hold the fd of a
closed socket. The test does not work in java because android framework
will force untag the socket before closing it.
Bug: 36374484
Test: run this test as CTS test and all devices should pass
Signed-off-by: Chenbo Feng <fengc@google.com>
Change-Id: I9e015d412d1aec10d843dfee4b480169d1f6ff8e
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)
IpSecManager and its associated classes are removed from OC.
They are planned for a future release.
Bug: 37681043
Test: make cts
Change-Id: I2ff911d5c62dbbf9be699330742d041706d9cbc2
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
