c37306ea65
Previously, VTS would run VtsHalWifiV1_0HostTest, a python script on the host that tries identify whether SoftAP and NAN should be supported by the device. This is complex, prevents migration to pure gtests without custom runners, and duplicates logic that has become available in VTS. This switches to equivalent methods natively available in VTS: - NAN: We can use "precondition-feature" to check for the "android.hardware.wifi.aware" feature. - SoftAP: We can use "precondition-lshal" to check whether the "android.hardware.wifi.hostapd" HAL is declared in the device manifest (should have the same semantics as the previous python check). This splits out NAN- and SoftAP-dependent parts of IWifiChip tests so that they can use this method, so some tests moved between these targets: - VtsHalWifiV1_0TargetTest - VtsHalWifiApV1_0TargetTest - VtsHalWifiNanV1_0TargetTest Bug: 142304083 Test: vts-tradefed run vts --primary-abi-only --skip-device-info -l DEBUG --include-filter VtsHalWifiV1_0Target --include-filter VtsHalWifiApV1_0Target --include-filter VtsHalWifiNanV1_0Target --include-filter VtsHalWifiV1_1Target --include-filter VtsHalWifiV1_2Target --include-filter VtsHalWifiV1_3Target --include-filter VtsHalWifiApV1_4Target Change-Id: Ica0b58811a0aa152c1a6c3c9a35d577d6ae70160 |
||
|---|---|---|
| .. | ||
| vts | ||
| Android.bp | ||
| IWifi.hal | ||
| IWifiApIface.hal | ||
| IWifiChip.hal | ||
| IWifiChipEventCallback.hal | ||
| IWifiEventCallback.hal | ||
| IWifiIface.hal | ||
| IWifiNanIface.hal | ||
| IWifiNanIfaceEventCallback.hal | ||
| IWifiP2pIface.hal | ||
| IWifiRttController.hal | ||
| IWifiRttControllerEventCallback.hal | ||
| IWifiStaIface.hal | ||
| IWifiStaIfaceEventCallback.hal | ||
| README-NAN.md | ||
| types.hal | ||