Windows Touch Test Lab (WTTL)
Updated: August 27, 2013
This article describes the Microsoft Windows Touch Test Lab (WTTL) for vendors and manufacturers of touch digitizers. It contains guidelines about how to use Microsoft testing facilities to certify the touch quality of a device to meet Windows Hardware Certification Program (formerly known as the Windows Logo Program) requirements.
This information applies for computers that run on Windows® 8 and Windows 8.1.
Microsoft introduced Windows Touch for Windows® 7 and extends Windows Touch in Windows 8 and Windows 8.1 to give users control of Windows and applications by using touch input. The WTTL is a Microsoft facility that is established to help partners ensure that their touch devices deliver high-quality touch experiences.
The Windows 8 Hardware Certification Requirements document defines Windows touch as a set of standards for devices and systems that support touch input. Because of the importance of the touch user experience, the Windows Hardware Certification Kit (Windows HCK) includes automated tests for Windows touch in addition to a suite of manual tests that include tapping, gesturing, and drawing lines and arcs on the touch screen.
Partners who build touch hardware must use the WTTL to run the Windows touch tests as the final validation step of touch device hardware certification. (Note that this validation step is not required for system submissions.)
|We recommend that you subscribe to the Windows Hardware Development Newsletters. These newsletters provide up-to-date news about the Windows Hardware Certification Program.|
WTTL hardware device certification overview
Before you can receive touch device certification for a device, you must generate a Windows HCK submission package by performing the touch tests in the Windows HCK. After you generate and submit a passing Windows HCK package, the WTTL runs a complete set of Windows touch tests by using the Windows HCK. During this testing, the WTTL uses high-precision assistant tools whenever possible to minimize human error. It tries each test item a maximum of two times.
If the device passes all tests, the WTTL passes the submission for certification of the touch device. If any tests fail, the WTTL stops the Windows HCK test and issues a report that lists the failed tests. You can choose whether to leave the device at the WTTL for future submissions.
WTTL sends an email receipt message when it receives a device. The Service Level Agreement is ten business days for WTTL to complete the certification on the condition that the submitted device does not have reliability or setup issues. Device issues that cause device setup or installation failures, or any unstable/unreliable device that prevents WTTL from completing certification tests, automatically results in a submission failure. We recommend that you reserve reasonable time in your product development cycle for both in-house touch testing and for the hardware certification process for devices and systems.
Microsoft provides the WTTL testing and certification service free of any additional charge beyond a standard submission fee. Microsoft will not make any details of the hardware, drivers, test results, or any other information about the submission available to any other company without your prior written approval. Microsoft returns submitted hardware upon request.
WTTL submission requirements
Microsoft does not test devices outside of the requirements for device certification. To ensure that touch performance is properly tested on a submitted device, device submissions to WTTL should meet the standards listed in the WTTL Submission Workbook. Prior to submission, validate all the items that are on the Submission Readiness Checklist tab of the WTTL Submission Workbook. You must also completely and accurately fill out the WTTL Submission Template tab of this workbook, and include it as part of the submission to WTTL.
How to submit a device to the WTTL
Follow the process that is described on the Directions tab in the WTTL Submission Workbook.
WTTL validation process
The WTTL uses the following process to validate devices for Windows touch hardware certification qualification:
Set up the device according to the submitted instructions.
Perform a clean install of Windows 8 together with all necessary drivers.
Load the Windows HCK software.
Run the touch tests that are listed for the touch device in the Windows HCK.
Validate each test by following the instructions in How to run the Windows HCK Tests for Touch and Pen Devices. Whenever possible, Microsoft applies high-precision assistant jigs and 9 mm diameter round styluses to minimize human error.
Test each item a maximum of two times. If all tests in the same category are successful on any attempt, WTTL proceeds to the next category of tests. If all tests are not successful, WTTL fails the submission.
For verification of panning latency, WTTL categorizes the devices into 3 different sizes, as follows:
Small form factor (smaller than 12”): run one time at the center of the digitizer.
Medium size device (12” ~ 17”): run two times on the digitizer (left and right, respectively).
Large size device (18” and above): Dissect the screen into tree even sections and run panning latency one time on each region respectively (left, center and right).
If the test result is above 15 ms but passes the Windows HCK test, WTTL reruns the test at the same location and if Windows HCK passes the second test pass also, WTTL passes the test.
- Small form factor (smaller than 12”): run one time at the center of the digitizer.
Touch hardware quality assurance
Windows 8 and Windows 8.1 touch devices must pass all hardware certification requirements for touch input to function. After a device has passed all of the tests, a hardware signature is issued, which allows Windows 8 and Windows 8.1 to identify the device as certified.
Prior to submission, Microsoft requires that a test signature be placed in firmware in the same location as the final release signature. This requirement guarantees that space is reserved for the release signature after it is granted, and provides a check that the signature is in the right location and can be read as expected. This is an important validation to perform, because the inability to read the release signature causes the device to not function. The tool to validate this is called GetTHQABlob.exe. The detail of sample BLOB injection as well as the GetTHQABlob.exe location and validation process can be found in Notes to the checklist in the WTTL Submission Workbook
ConceptsWindows Touch Testing Prerequisites
Other ResourcesLearn About Windows Hardware Design and Development
Windows Certification Program Policies and Processes
Windows Dev Center - Hardware Dashboard Services
How to Use the Precision Touch Testing Tool
Overview of Measuring Touch Down Hardware Latency
Overview of Measuring Touch Panning Hardware Latency
How to Measure Touch Panning Latency
How to Measure Touch Down Latency