| e768fb9cea24dc184490c2dac6058c5f08d60313 |
|
09-Feb-2018 |
Zhuoyao Zhang <zhuoyao@google.com> |
Convert wifi hal test to use VtsHalHidlTargetTestEnvBase
Bug: 64203181
Test: make vts
vts-tradefed run vts -m VtsHalWifiV1_0Host
vts-tradefed run vts -m VtsHalWifiV1_1Target
vts-tradefed run vts -m VtsHalWifiSupplicantV1_0Target
vts-tradefed run vts -m VtsHalWifiSupplicantV1_1Target
Change-Id: I4ea9554829b75b73b600ab668885d57c94251a87
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 2d6676a1ce9083876f45dd1e581f7007c7531406 |
|
17-Nov-2017 |
Roshan Pius <rpius@google.com> |
wifi(vts): Ignore HAL stop failure
The stop may fail if the interface down operation takes too long on some
devices. This is not fatal as long as we're able to bring up the
interfae for the next HAL start.
Bug: 68303248
Test: VTS tests
Change-Id: I93943f9d0cfb83cf07253c6f9b3866d6d137028f
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 8c216524a3876fc48ec903671f5ae756050ec3e0 |
|
04-Aug-2017 |
Roshan Pius <rpius@google.com> |
wifi(vts): Ignore IWifi.stop() returning ERROR_NOT_AVAILABLE
When IWifi.stop() is invoked back to back (happens in the ConfigureChip
vts test), the HAL would return ERROR_NOT_AVAILABLE if the previous stop
is still being processed. This is not an error that needs to fail the test,
but a legitimate status for stop. We have a retry mechanism to handle
this in both the VTS test and framework for the case where IWifi.start()
is invoked while the previous stop is being processed.
While there, corrected a few log messages emitted by the HAL to debug
such startup/stop issues better.
Bug: 63971806
Test: `vts-tradefed run commandAndExit vts --skip-all-system-status-check
--primary-abi-only --skip-preconditions --module VtsHalWifiV1_0Target -l
INFO`
Change-Id: I5e3470ac97541a6ea10aceec9b737e5d03ed5206
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| c802e09390844e0129ca30843b9e25e7ae33cc11 |
|
22-May-2017 |
Roshan Pius <rpius@google.com> |
wifi(vts): Add retry for HAL start
Port of the retry logic added in HalDeviceManager for temporary IWifi.start()
failures when invoked immediately after IWifi.stop().
Bug: 38342536
Test: Run VTS tests
Change-Id: Ie58a08c45979bafa0c61fa1c8536a2c0a0cd8ed9
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 2d523c012e16e62d73bde73d853421826aae278f |
|
23-Mar-2017 |
Etan Cohen <etancohen@google.com> |
[WIFI] Restore initialization code
Restore the usage of WIFI-specific main function. The main
function was inadvertantly disabled by moving it into a static
library - which caused the default main to be used.
Need a custom main since need to stop WIFI before tests start
to enforce a clean starting point.
Bug: 35276551
Test: confirms custom main routine is called
Change-Id: I978827bc0f0f16d9ca4f159fbf42d0bc53f5df99
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 6b8720110bf2d40ac1364c364a85c31b358889f1 |
|
10-Mar-2017 |
Yuexi Ma <yuexima@google.com> |
Change vts target base test class name
Test: make vts succeed, vts kernel tests and nfc hal tests passed
Change-Id: I38ae6cc940d0f17bb3352f360efdf9c70697c76b
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 3819e4193e5ffd869c92a83a2adf29d5ada146fb |
|
09-Dec-2016 |
Roshan Pius <rpius@google.com> |
wifi(vts): Some IWifiChip/IWifiStaIface tests
These tests basically just ensure that we can call the corresponding
API's successfully. More tests will be added in further CL's.
Bug: 33459306
Test: mmm -j32 hardware/interfaces/wifi/1.0/vts/functional/
&& adb push out/target/product/angler/data/nativetest64/
VtsHalWifiV1_0TargetTest/VtsHalWifiV1_0TargetTest /data/ &&
adb shell /data/VtsHalWifiV1_0TargetTest
Change-Id: I12ad26653993ce7167d007a887e7aff07fd0a5ce
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 80054133dc500ab0c460d9b4e146cf70db7a6f0a |
|
13-Feb-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] VTS baseline
Modified Wi-Fi test setup/tear-down to shutdown and start the
Android framework. The framework competes with the VTS to control
the HAL and so must be disabled for the duration of the test.
Added framework to support VTS testing with the Wi-Fi Aware (NAN)
interface.
Added all callback types (notifications, events) with ability to
wait for such callbacks.
Bug: 35276551
Test: gtest pass
Change-Id: I50847fccad457c2b225ba7f2e1760b4dbb4d363f
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 93d2541aaeac5b2d5238628e5cc13339f6863685 |
|
28-Feb-2017 |
Yuexi Ma <yuexima@google.com> |
Add columns to namespace for vts target base test invocation
Test: make vts
Change-Id: Ia0284fbc11eadef572dd510bb5847160852bd517
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 178dfd5e291ed78921bd0c21b4203ff75406ae04 |
|
24-Feb-2017 |
Yuexi Ma <yuexima@google.com> |
change all vts hidl tests to use VtsHalHidlTargetBaseTest
Bug: 33385836
Test: mma
Change-Id: I660d6e0fce6422d87d4b227273a77c95d20ed3f2
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 90f321722ce37554fb70481f44f8b4a32389a9e6 |
|
26-Jan-2017 |
mukesh agrawal <quiche@google.com> |
wifi(vts): simplify HIDL calls
Presently, the core of the Wifi test logic is
obscured by the boilerplate required to create
a callback.
This CL provides some utilities to simplify
the creation of a HIDL result callback, and
migrates existing Wifi code to use the new
utilities.
Along the way: add a .clang-format file, so
that I don't misformat code with 2-space
indents (the Google default).
Bug: 34817351
Test: vts-tradefed run commandAndExit vts --module=HalWifiHidlTargetTest
Change-Id: Id2c728f96c3369c74adc8dfce7228b0a15a0781e
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| ab8166fa4e08d8f86504bb7311b86e31cd839cb1 |
|
19-Jan-2017 |
Chris Phoenix <cphoenix@google.com> |
wifi HAL uses "default" service name
The getService() and registerAsService() methods of interface objects
now have default parameters of "default" for the service name. HALs
will not have to use any service name unless they want to register
more than one service.
Test: builds; verify HAL still works
In support of b/33844934
Change-Id: Ia086509b3433976524bc4a0ac4b24385840ce565
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|
| 1ae4cbbb82d778a8945c78a569331c1616842bef |
|
07-Dec-2016 |
Roshan Pius <rpius@google.com> |
wifi(vts): Add framework for gtests
These tests don't do much currently other than assert that we can
configure the chip in the required modes and create all the iface
objects.
The |wifi_hidl_test_utils| contains all helper functions that will be
shared across the different test fixtures.
Bug: 33459306
Test: adb root && adb remount && adb push
out/target/product/angler/data/nativetest/wifi_hidl_test/wifi_hidl_test
/data/ && adb shell /data/wifi_hidl_test
Change-Id: Iaea8e264ab1ef9113f375d7f56acab851aff21aa
/hardware/interfaces/wifi/1.0/vts/functional/wifi_hidl_test_utils.cpp
|