NDISTest 6.5 - WLanAssociation

This automated test associates and disassociates wireless LAN keys.

Test details

Associated requirements

Device.Network.WLAN.Base.ConformToNDIS Device.Network.WLAN.Base.MeetScanAndConnReq Device.Network.WLAN.Base.OnlyWDFOrNDIS630Calls Device.Network.WLAN.Base.PermitIEToRequestAndResponseAF Device.Network.WLAN.Base.SupportVirtualWiFi Device.Network.WLAN.CSBBase.ConformToNDIS Device.Network.WLAN.CSBBase.MeetScanAndConnReq Device.Network.WLAN.CSBBase.OnlyWDFOrNDIS630Calls Device.Network.WLAN.CSBBase.PermitIEToRequestAndResponseAF Device.Network.WLAN.CSBBase.SupportVirtualWiFi Device.Network.WLAN.CSBSoftAP.SupportSoftAP Device.Network.WLAN.SoftAP.SupportSoftAP

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

~12 minutes

Categories

Certification Functional

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 in this test:

  • Association_cmn

  • Association_ext

  • Disassociate_cmn

The Association_cmn suite consists of the following:

NameDescription

Pre-configuration

  • Start testsoft access point

  • Query supported authentication/cipher types

  • Ignore open none

  • Start access point comm helper

  • Start DUT comm helper

VerifyAssociateWithDifferentPHY

Configure access point for each PHY type support by DUT and then verify that the DUT can successfully connect by using each PHY type.

VerifyResetWhileJoinAdhoc

Verify the DUT can successfully handle a reset while attempting to connect to IBSS.

VerifyAssociateWithSpecifiedNetwork

Verify the association information when connected to an IBSS network.

VerifyAssociateWithOneAPConfiguredToReject

Verify the DUT can successfully connect to a different access point in the same ESS if a connection attempt is rejected by the first access point.

Verify32BytesSSID

Verify the DUT can successfully connect to an access point with a 32 byte SSID.

VerifyAssociateWithApStaAp

Verify the DUT can successfully switch between AP and IBSS networks.

VerifyAssociateWithBSSAP

Verify the DUT can successfully connect to an access point when an IBSS is present with the same SSID. This is not applicable to devices that support InstantGo.

UnloadLoadAssociate

Verify the DUT can successfully connect after a driver was loaded or unloaded.

AssociateUnloadLoad

Verify the DUT can successfully load and unload while connecting.

VerifyDriverUnloadDuringConnect

Unload the miniport driver while the DUT is attempting to connect and then verify the driver unloads successfully.

VerifyDriverResetDuringConnect

Verify the DUT successfully resets while attempting to connect to an access point.

VerifyAssociateWithAPRejection

Verify the DUT can successfully handle an association rejection from an access point.

VerifyAssociateWithAPDeauthenticate

Verify the DUT can successfully handle a deauthentication from an access point while associating.

VerifyAssociateWithAPDisassociate

Verify the DUT successfully handles a disassociate from an access point while associating.

VerifyAssociateWithAPIgnoreRequest

Verify the DUT successfully handles no association response from an access point.

 

The Association_ext suite consists of the following:

NameDescription

Pre-configuration

  • Start testsoft access point

  • Query supported authentication/cipher types

  • Ignore open none

  • Start access point comm helper

  • Start DUT comm helper

Before set OID_DOT11_ASSOCIATION_PARAMS, associate DUT and get default IEs.

Get the default IEs.

After set OID_DOT11_ASSOCIATION_PARAMS, associate DUT and get IEs.

Set one custom IE and then verify it.

After set OID_DOT11_ASSOCIATION_PARAMS, associate DUT and get IEs.

Set two more custom IEs and then verify all three.

After reset OID_DOT11_ASSOCIATION_PARAMS, associate DUT and get IEs.

After reset, verify that the custom IEs are gone.

 

The Diassociate_cmn suite consists of the following:

NameDescription

Pre-configuration

  • Start testsoft access point

  • Query supported authentication/cipher types

  • Ignore open none

  • Start access point comm helper

  • Start DUT comm helper

VerifySTADisassociation

Verify the DUT successfully indicates a disconnection after receiving OID_DOT11_DISCONNECT_RESET.

VerifyAPDisassociate

  • Clearing all actions on the access point, connect to the DUT to the access point, and then configure the access point for BeaconOnly action to prevent the DUT from associating again.

  • Verify the DUT successfully indicates a disconnection after receiving a disassociate frame from the access point.

VerifyAPDeauthenticate

Verify the DUT successfully indicates a disconnection after receiving a disassociate frame from the access point.

VerifyAPLoseConnection

Verify the DUT successfully indicates a disconnection when the access point is no longer available.

 

Troubleshooting

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

 

 

Send comments about this topic to Microsoft

Show: