Adjust some timeout value and correct the conditional checking
for private DNS waiting mechanism.
Also move the fail() statement from callback thread to test thread.
It is used to avoid the test process crashing.
Bug: 148471807
Test: atest DnsResolverTest
Change-Id: I244cefeae97fe99838d1c72d867c1d7a1a7d5e87
p2p does not use NetworkInfo.isAvailable() anymore.
Remove this obsolete check.
Bug: 148164038
Bug: 148561948
Test: atest android.net.wifi.cts.ConcurrencyTest
Change-Id: I544a2363d85ea47e404e481d4d285b9fd6b38eb5
Test files will be under ipsec/src/android/net/cts and
ipsec/src/android/net/ipsec/ike/cts
Bug: 148689509
Test: atest CtsNetTestCases(passing)
Change-Id: I1f79b0515708fcd31fd8ea9aa3974dcdcfb265c9
Before this change the test assume one active state event is followed by
zero or one availabe event:
AVAIALBE(wlan1) -> ACTIAVE(wlan1) -> AVAILALE(wlan1)
But actually Multiple tetherable wifi interfaces may be avaialbe during
the test:
AVAILABLE(wlan1) -> AVALIABLE(wlanX) -> .... -> ACTIVE(wlan1) ->
AVAIALBE(wlan1)
Additional, replacing ConnectivityManager usage to TetheringManager.
Bug: 148095484
Test: atest CtsTetheringTest
Change-Id: Id5db970c02f63f61802a18b599bf6905db619b42
This APK can be installed and run on release devices even when
built from branches with a non-final SDK such as AOSP.
Test: builds
Change-Id: I1e1b24b09eeb7a0688fde9d8ed6bbee9c9d2582e
Verify that ConnectivityDiagnosticsManager is able to register and
unregister ConnectivityDiagnosticsCallbacks.
Bug: 143187964
Test: atest ConnectivityDiagnosticsManagerTest
Change-Id: Ica065b58ee47e088b9d85b09f9e5b7131f5a16ab
The testcase is failing for the model as there are no clients which have already invoked the initialize API.
So we changed the location of initialize() API little forward to be invoked before CTS test.
Bug: 148126151
Test: run cts --m CtsNetTestCases --t android.net.wifi.cts.ConcurrencyTest#testConcurrency
Change-Id: I1081d343795e07440ebf380c25f47c320c064556
Signed-off-by: Jae Choon Jeon <jc.d.jeon@samsung.com>
(cherry picked from commit 1a46560a2b55df0b3159884a7eed4b2598c2e827)
Marks this CTS test module as supporting secondary_user, meaning that
the tests are eligible to be run from a regular Android user other
than the system user (i.e. other than user 0).
Note that 'user' here refers to the concept of users in Android
Multiuser; it is NOT the same as a uid.
Bug: 141773058
Test: module passed with secondary_user params
(--enable-optional-parameterization --module-parameter secondary_user)
Change-Id: I92d97cae99418dac3cd6e1cbb625b12f0c2cc60a
This test case stop when detect a app failure once a time, which cannot find out all app failure. Use StringBuilder to collect failure info of all apps first, if the StringBuilder is not empty then print all the failure info.
Bug:145475188
Test: run cts -m CtsNetTestCases -t android.net.wifi.cts.WifiManagerTest#testNetworkSettingsPermission
Change-Id: I0e49b65bbe7deca82edd1908dfb6f221551ff725
Signed-off-by: qianyou <qianyou@xiaomi.com>
(cherry picked from commit dcb3a18cbf81f2970d6c3b23a478da5b4ba91805)
Soong wasn't including android_app or android_test sources in the
javac-check target used for the Error Prone build, which allowed
some Error Prone errors to get in. Fix them so Error Prone can be
re-enabled for these targets.
Fixes:
cts/hostsidetests/devicepolicy/app/DeviceAndProfileOwner/src/com/android/cts/deviceandprofileowner/LockTaskHostDrivenTest.java:50: error: [JUnitAmbiguousTestClass] Test class inherits from JUnit 3's TestCase but has JUnit 4 @Test annotations.
cts/hostsidetests/devicepolicy/app/DeviceAndProfileOwner/src/com/android/cts/deviceandprofileowner/LockTaskTest.java:51: error: [JUnitAmbiguousTestClass] Test class inherits from JUnit 3's TestCase but has JUnit 4 @Test annotations.
cts/tests/tests/telephony/current/src/android/telephony/cts/CarrierServiceTest.java:34: error: [JUnitAmbiguousTestClass] Test class inherits from JUnit 3's TestCase but has JUnit 4 @Test annotations.
cts/tests/tests/tethering/src/android/tethering/cts/TetheringManagerTest.java:166: error: [ArrayToString] Calling toString on an array does not provide useful information
cts/tests/tests/tethering/src/android/tethering/cts/TetheringManagerTest.java:172: error: [ArrayToString] Calling toString on an array does not provide useful information
Bug: 146455923
Test: m RUN_ERROR_PRONE=true javac-check
Change-Id: I949e409fd7ba80ab8937db1c08eaaaf9608b17ed
Initial CTS test for tethering.
This change test startTethering/stopTethering and check
status of TETHER_STATE_CHANGE intent.
Bug: 145490751
Test: atest CtsTetheringTest
Change-Id: Ia1ae3b6c2b68b009ca4deef840945186d472d99e
Add test for new public APIs
Test: atest android.net.cts.MacAddressTest
Bug: 139268426
Bug: 135998869
Change-Id: Ib2b73851f621f1648904276ec12ceea02f4b5970
am skip reason: Change-Id Ifa2710aed7e773a24786cc3e4912f126547dfe0b with SHA-1 3b160e2385 is in history
Change-Id: I7182910f244b1c0adcb254adeb6fb5c20da5f4d4
am skip reason: Change-Id Ifa2710aed7e773a24786cc3e4912f126547dfe0b with SHA-1 3b160e2385 is in history
Change-Id: I74865316a615b0a7e96b02b61133dc03cb8bec15
am skip reason: Change-Id Ifa2710aed7e773a24786cc3e4912f126547dfe0b with SHA-1 3b160e2385 is in history
Change-Id: I351adf65d7cefb1a97ddee9a80ed9978b28d0187
