| Test Suite | Scope | Environment | Guide |
|---|---|---|---|
| Crate Unit Tests | Algorithms, frame parsers, crypto handshakes, and state machines in lib/*, wlancfg, wlanix, wlandevicemonitor | Host or hermetic component sandbox | ../lib/README.md |
| WLAN Core | Core stack components without policy layer | Hardware testbed | core/README.md |
| WLAN Policy | Policy behaviors, auto-connect, network selection, roaming | Hardware testbed | wlancfg/ |
| WLANIX | Android WiFi HAL implementation for Starnix | Hardware testbed | wlanix/README.md |
| E2E Automation | Executing and debugging test suites | Local / remote testbeds | E2E Skill |
WLAN end-to-end tests are host-driven Lacewing tests and require the device under test to be flashed with the corresponding testing product bundle (for-testing-wlan-core.<board>, for-testing-wlan-platform.<board>, or for-testing-wlan-wlanix.<board>).
For DUT-only tests, add the host test target and run it like any other Fuchsia test via fx test:
fx add-host-test //src/connectivity/wlan/tests/core:phy_existence_test fx test --build --e2e --output //src/connectivity/wlan/tests/core:phy_existence_test
For tests that require an Access Point (reachable over SSH directly or via port forwarding), pass the Access Point SSH parameters after --:
fx add-host-test //src/connectivity/wlan/tests/core:connect_to_ap_test fx test --build --e2e --output //src/connectivity/wlan/tests/core:connect_to_ap_test -- \ --ap-ip <IP address> --ap-ssh-port <port>
--ap-ip generates an OpenWrtAP controller configuration by default.--ap-ssh-port defaults to 22 if omitted.--ap-ssh-key <path> can be passed to specify a custom SSH private key for the Access Point (if omitted, mobly_driver searches ~/.ssh/openwrt_testing_rsa and ~/.ssh/testing_rsa).To run a subset of test cases within a test suite, pass --test_cases after --:
fx test --build --e2e --output //src/connectivity/wlan/tests/core:connect_to_ap_test -- \ --ap-ip <IP address> --ap-ssh-port <port> \ --test_cases 're:.*SecurityOpen.*'