Partager via


NDISTest 6.5 - WlanRoaming

This automated test suite verifies the device can roam under various circumstances, such as losing connection to the access point, the access point is not responding. The test suite also verifies that the device does not roam to an IBSS configured with the same SSID as the access point.

Test details

Associated requirements

Device.Network.WLAN.Base.MeetScanAndConnReq Device.Network.WLAN.CSBBase.MeetScanAndConnReq

See the device hardware requirements.

Platforms

Windows 7 (x64) Windows 7 (x86) Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86

Expected run time

~14 minutes

Categories

Certification Reliability

Type

Automated

 

Running the test

Before you run the test, complete the test setup as described in the test requirements: Wireless LAN (802.11) Testing Prerequisites.

The following suites are available:

  • Roaming_cmn

The Roaming_cmn suite consists of the following:

Name Description

VerifyBssidNotInScanList

Verify the BSSID is removed from the scane list of the DUT within 30 seconds after the access point is powered down

VerifyFailoverRoaming

Verify the DUT can successfully connect with another access point in the same ESS after losing connection with the current access point.

VerifyPowerSaveRoaming

Verify the DUT roams to a new access point after the original access point disappears during standby.

VerifyProfileRoaming

After a request from the operating system, verify the DUT connects to a new access point or SSID after the original access point disappears during standby.

VerifyPowerSaveRoaming

Verify the DUT roams to a new access point after the original access point disappears during hibernate.

VerifyProfileRoaming

After a request from the operating system, verify the DUT connects to a new access point or SSID after the original access point disappears during hibernate.

 

Troubleshooting

For troubleshooting information, see Troubleshooting Wireless LAN (802.11) Tests.

 

 

Send comments about this topic to Microsoft