| 1fd43a9ace3814f13f4a865878c9c11fe5cdd18b |
|
23-Apr-2018 |
Rebecca Silberstein <silberst@google.com> |
update wifi unit test scripts
Need to add "--no-hidden-api-checks" to unit test scripts.
Verified by running both runtests and coverage scripts
Bug: 78465388
Test: frameworks/opt/net/wifi/tests/wifitests/runtests.sh
Test: adb shell am instrument -e coverage true --no-hidden-api-checks -w 'com.android.server.wifi.test/com.android.server.wifi.CustomTestRunner'
Change-Id: Ice1b62ce035c52d159d9fc2cc83dd5c962cd490f
/frameworks/opt/net/wifi/tests/wifitests/runtests.sh
|
| 733b3be54f22c9823f1202837255f77d9d008b1c |
|
14-Dec-2017 |
mukesh agrawal <quiche@google.com> |
tests: remove DisabledForUpdateToAnyMatcher
This annotation class is no longer needed. Nuke it.
Bug: 36658432
Test: runtests.sh
Test: runtests.sh -e class com.android.server.wifi.WifiDiagnosticsTest
Change-Id: I78378b9bd01f9fae145e66ea293affb0f2344123
/frameworks/opt/net/wifi/tests/wifitests/runtests.sh
|
| d9b2ef1b267206c2ef353aa352bdffdedefdd532 |
|
14-Apr-2017 |
mukesh agrawal <quiche@google.com> |
tests: don't crash on Log.wtf() in eng builds
We'd like to be able to run the unit tests on eng builds,
and get meaningful results. Unfortunately, at the moment,
any test that excerises a call to Log.wtf() will cause
the tests to abort (not fail -- abort).
The abort happens because Log.wtf() aborts on eng builds
(by design). While that likely makes sense for normal
code, it gets in the way of testing.
Resolve this, by installing a custom TerribleFailureHandler
before running our tests.
Note that this does mean that our code behaves differently
under eng-test than eng-normal. I think we're okay with that,
since the eng-test behavior now more closely reflects the
user-normal and userdebug-normal behavior.
Bug: 36981745
Test: tests/wifitests/runtests.sh (on aosp_bullhead-eng)
Change-Id: Ieb3a3a98eacdf7131efd1efc6a966f68724e701b
/frameworks/opt/net/wifi/tests/wifitests/runtests.sh
|
| da7d73da44a47933cfc99660c2d247c24fd72544 |
|
24-Mar-2017 |
mukesh agrawal <quiche@google.com> |
disable failing tests
Disable failing unit tests, except for the ones where
a) we already have fixes up for review, or
b) the test was failing before the Mockito update
The tests are disabled via a new annotation, so that
we can more easily track progress on updating the
tests to work with the new version of Mockito.
Bug: 36407367
Test: runtests.sh -e notClass com.android.server.wifi.WifiVendorHalTest,com.android.server.wifi.hotspot2.PasspointManagerTest,com.android.server.wifi.WifiConfigManagerTest,com.android.server.wifi.p2p.SupplicantP2pIfaceHalTest#testCancelServiceDiscovery_exception
Change-Id: Idca42fe735821a29a6dc0ca975bf5d39909ec508
/frameworks/opt/net/wifi/tests/wifitests/runtests.sh
|
| 0db50e20ec8d91c5febed969f01cb4cb53ee2288 |
|
21-Feb-2017 |
mukesh agrawal <quiche@google.com> |
runtests.sh: add help option
While the default behavior of runtests.sh is the
correct one (run _all_ the tests), there are some
other common use cases.
Add a "--help" option, which explains how to perform
other common tasks.
Bug: 35632708
Test: ./runtests.sh
Test: ./runtests.sh -r -e class com.android.server.wifi.WifiDiagnosticsTest#startLoggingRegistersLogEventHandler
Change-Id: I0f823bfbe271069b8af4aa9ec3bbd6074113ad3d
/frameworks/opt/net/wifi/tests/wifitests/runtests.sh
|
| 67b1811188b7a874bb851dddc3b3cd930a551773 |
|
01-Jul-2016 |
Mitchell Wills <mwills@google.com> |
Add script to automatically build, deploy and run wifi unit tests
Change-Id: I8a791254272fa3986d1f366b638664f98f229cff
/frameworks/opt/net/wifi/tests/wifitests/runtests.sh
|