tests: Fix connect_cmd_roam with old scan results

connect_cmd_roam did not force a new scan to find the second AP. This
could result in failures due to the ROAM command getting rejected, e.g.,
in the following test case sequence: wext_pmksa_cache connect_cmd_roam.

Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
Jouni Malinen 2015-10-04 00:35:12 +03:00
parent cd27374f5f
commit 7d56bd734c

View file

@ -149,5 +149,5 @@ def test_connect_cmd_roam(dev, apdev):
wpas.connect("sta-connect", key_mgmt="NONE", scan_freq="2412")
hostapd.add_ap(apdev[1]['ifname'], params)
wpas.scan_for_bss(apdev[1]['bssid'], freq=2412)
wpas.scan_for_bss(apdev[1]['bssid'], freq=2412, force_scan=True)
wpas.roam(apdev[1]['bssid'])