Hardware Dev Center

Collapse the table of content
Expand the table of content
Expand Minimize

WHCKProximityTest- TagWritingTypesDisallowed

This automated test determines whether the proximity implementation does not process disallowed protocols.

Test details

Associated requirements

Device.BusController.NearFieldProximity.ProviderImplementation

See the device hardware requirements.

Platforms

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

~2 minutes

Categories

Basic Certification Functional

Type

Automated

 

Running the test

Before you run the test, complete the test setup as described in Proximity Controller Testing Prerequisites.

Troubleshooting

For troubleshooting information, see Troubleshooting Bus Controller Testing.

More information

This test is run against a single test computer.

Command syntax

Command optionDescription

Te.exe /inproc WHCKNearFieldInitiator.dll /name:”CWHCKProximityTestInitiator::TagWritingTypesDisallowed”

Runs the test.

 

Note  

For command-line help for this test binary, type the following:

Te.exe /inproc WHCKNearFieldInitiator.dll /name:”CWHCKProximityTestInitiator::TagWritingTypesDisallowed” /listproperties

File list

FileLocation

Te.exe

<TAEFBinRoot>

WHCKNearFieldInitiator.dll

<testbinroot>\dtmtest\NearField\

 

 

 

Community Additions

ADD
Show:
© 2015 Microsoft