| 58a3ddf5aafacbd84de7104f07a994bb06a9b374 |
|
23-Oct-2014 |
Eric Rowe <erowe@google.com> |
Add delay in ping connectivity test retry
Change-Id: Id6e36f42b2a2d84605185780fb7a3f2144e7a9b9
/frameworks/base/core/tests/ConnectivityManagerTest/src/com/android/connectivitymanagertest/ConnectivityManagerTestBase.java
|
| 86e15557c52e2847d2adc8495a281dcf0239506e |
|
10-Sep-2014 |
Eric Rowe <erowe@google.com> |
Allow protected wifi in connectivity tests
Change-Id: I31285572f90bfb46cc28fb04e79cb9b407477a7d
/frameworks/base/core/tests/ConnectivityManagerTest/src/com/android/connectivitymanagertest/ConnectivityManagerTestBase.java
|
| f5031e549472d1d813fa39b6b2973cd20c1b1120 |
|
06-Sep-2014 |
Eric Rowe <erowe@google.com> |
Increase long timeout to 2 minutes
Change-Id: I2f9e15c6e551536d61ec52fbaf7f54405fa05bcd
/frameworks/base/core/tests/ConnectivityManagerTest/src/com/android/connectivitymanagertest/ConnectivityManagerTestBase.java
|
| 2591e00b57b8aedd9e44fecce3f55a2c6a5428c2 |
|
03-Sep-2014 |
Eric Rowe <erowe@google.com> |
Clean up connectivity tests.
Change-Id: I407cb78aecb43aa8413835a25b4558241d69fd2e
/frameworks/base/core/tests/ConnectivityManagerTest/src/com/android/connectivitymanagertest/ConnectivityManagerTestBase.java
|
| 4afd179a9ad7da51374c6fb0887180976d952001 |
|
21-Aug-2014 |
Guang Zhu <guangzhu@google.com> |
follow up minor fixes for connectivity manager test
Change-Id: I8f0606890b21d67130efb3bc02c6825823060139
/frameworks/base/core/tests/ConnectivityManagerTest/src/com/android/connectivitymanagertest/ConnectivityManagerTestBase.java
|
| d21f1c1e4d34306ab7aa99f5be1b886f6b4e07a8 |
|
19-Aug-2014 |
Guang Zhu <guangzhu@google.com> |
fixes for connectivity manager test suite
* reduced visibility of most util functions in
ConnectivityManagerTestBase
* reimplemented various waitFor... util function in base class:
instead of relying on received broadcast and synchronization
mechanism, we just poll for what we want with a fixed interval
and a max timeout
* minor style fixes
* removed state transition checks in all test cases of
ConnectivityManagerMobileTest: since exact state transitions
are not that interesting, we just care about if we reach a
particular state and if all network interfaces are in their
corresponding states
* clarified in comment what each test cases are testing, since
some of the test case names are not very straightforward
* any wait for DISCONNECTED checkes with ConnectivityManager are
temporarily commented out
Change-Id: I99cca95c33c6060909e0df684969b75c2dca23a9
/frameworks/base/core/tests/ConnectivityManagerTest/src/com/android/connectivitymanagertest/ConnectivityManagerTestBase.java
|
| 19306af73a8175e1327101132e26a35c7dfe5168 |
|
14-Sep-2013 |
Xia Wang <xiaw@google.com> |
Update the Connectivity Manager test suit to use InstrumentationTestCase.
- Remove ConnectivityManagerTestActivity as the test activity could be destroyed
after a system config change, which cause test failure in the wifi stress test.
- Update all tests to use InstrumentationTestCase, which instruments the test package.
Bug : 10426067
Change-Id: Ibf6f1f7cffd7a7eabc4cc63c7e033b59274b724e
/frameworks/base/core/tests/ConnectivityManagerTest/src/com/android/connectivitymanagertest/ConnectivityManagerTestBase.java
|