Windows Touch Test
This test verifies that a Windows Touch device meets requirements.
Test details
| Specifications |
|
| Platforms |
|
| Supported Releases |
|
| Expected run time (in minutes) | 2 |
| Category | Compatibility |
| Timeout (in minutes) | 120 |
| Requires reboot | false |
| Requires special configuration | false |
| Type | automatic |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
Running the test
Before you run the test, complete the test setup as described in the test requirements: Windows Touch Testing Prerequisites.
The Windows Touch Test combines a set of simple manual tests. Measured requirements include: having a bezel that is flush with the display, specifying physical dimensions that match the device's true physical dimensions, and passing the HID Validator tool's static test. (The HID Validator tool installed together with the Windows HLK).
Flush Bezel
The bezel requirement (System.Client.Digitizer.Touch.Bezel) helps ensure easy access to the edge of the screen, which is used to display the Charms Bar and to switch applications. It also provides an optimal set of conditions to use the thumb keyboard. USB and I2C buses are required because they support the HID standard upon which the Windows touch infrastructure is based. FFU is required.
For a Tablet device, ensure that the bezel is flush with the display (the bezel must not be taller than the display).
Physical Dimensions
The physical dimensions of the device must support system gestures and general touch interactions (Device.Digitizer.Touch.PhysicalDimension). For example, the momentum of a touch gesture depends on the physical distance moved and the length of that movement.
This test verifies that the physical dimensions that are reported by the HID descriptor match the true physical dimensions of the visible screen area. Discrepancies affect system gestures and UI elements, which rely on physical size information. We strongly recommend that you use the dimensions that are specified by the display manufacturer. The test itself relies on this information to size elements appropriately. The test will be affected by errors; for example, targets that are intended to be 20mm apart might resolve to being 22mm apart. The WTTL does not make allowances for devices that report physical size values that differ from the true measurement by more than 2mm.
High Quality Touch Digitizer Input
To run this test, the HID descriptor must be stored in the device firmware. The Windows Hardware Lab Kit (Windows HLK) includes the HID Validator tool. Before you run this test, we recommend that you review Windows Hardware Certification Requirements and the HID Validator documentation that is installed together with the HID Validator tool.
To run the test, double-click HidValidator.exe on the touch device. The tool ensures that the descriptor conforms to the HID specification.
Power States
For a discussion of power-state requirements (Device.Digitizer.Touch.PowerStates), see Power Handling for Windows 8 Touch Controllers.
You can use the WTTL to check the ability of a device to traverse power states by using the following procedure:
To run the power states test
If applicable, put the device into the Connected Standby state. Otherwise, power the device off.
Place any type of contact on any number on the screen and hold for 10 to 15 seconds.
If the device is in the Connected Standby state, wake the device while maintaining contact. If the device is powered off, power on the device while maintaining contact.
After the machine has booted, ensure that no ghost touches exist. Attempt to use touch input.
If applicable to the device, repeat these steps for Sleep (S3) state.
If no ghost touches exist, and if touch input can be used as expected to control the machine, then the device passes this test. Otherwise, it fails the test.
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.
For troubleshooting information, see Troubleshooting Device.Input Testing and the Hardware Component Guidelines for Windows Digitizer Class Input Devices.
More information
Command syntax
| Command option | Description |
|---|---|
Logo3.exe -config Other.json |
Runs the test. |
File list
| File | Location |
|---|---|
Logo3.exe |
<testbinroot>\digitizer\Win8Touch |
Other.json |
<testbinroot>\digitizer\Win8Touch |