Digitizer Testing Prerequisites
This section describes the tasks that you must complete before you test a digitizer for Windows 8 by using the Windows Hardware Certification Kit (Windows HCK).
In this topic:
To learn more, go to Windows Certification Program Polices and Process
To test a digitizer, you must have the following hardware. You might need additional hardware if the test device offers other features. To determine whether additional hardware requirements apply, see the test description for each test that appears for the device in Windows HCK Studio.
One test computer that meets the Windows HCK prerequisites. For more information, see Windows HCK Prerequisites.
The digitizer device to be tested.
One USB hub that is Windows Certified if the digitizer is a USB-based device.
To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. You do not need a computer that actually has more than 64 processors to test your device. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. For more information see Windows Server Installation Options.
If you use a pool of test computers to test devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. As long as the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers.
For tests that do not include a driver to test, such as hard disk drive tests, the Windows HCK scheduler constrains the tests that validate the device’s and driver’s Rebalance, D3 State and Multiple Processor Groups functionality to run on the default test computer. You must manually configure this computer to have multiple processor groups. The default computer is the first test computer in the list. Test personnel must make sure that the first test computer in the list meets the minimum hardware requirements.
Except for para-virtualization drivers (as defined by Logo Program Requirement Policy-0020), you may not use any form of virtualization when you test physical devices and their associated drivers for server certification or signature. All virtualization products do not support the underlying functionality that is required to pass the tests that relate to multiple processor groups, device power management, device PCI functionality, and other tests.
To test a digitizer, you must have the following software:
Windows Server 2008 R2
The drivers for the test deviceNote
You cannot install any touch drivers. You must have correct drivers for other components in the test device that affects testing, such as a graphic driver.
The latest Windows HCK filters or updates
To configure the test computer for your test device, follow these steps:
Install the appropriate Windows operating system on the test computer, and then configure the computer for your test network. The test network is the network that contains Windows HCK Studio and Windows HCK Controller.
If the test device is connected through the USB port, connect the USB 2.0 controller to the high-speed USB 2.0 hub, and then connect the test device to the downstream port of the high-speed USB 2.0 hub.Note
Don't connect the USB test device directly to the root hub of the USB 2.0 controller.
Attach the digitizer device to be tested to the test computer.
Install the manufacturer-supplied device driver, if the device requires one, on the test computer.Note
For touch digitizer, there should be no touch drivers installed.
Verify that the digitizer functions correctly on the digitizer device to be tested.
Install the Windows HCK client application on the digitizer device to be tested.
Use Windows HCK Studio to create a computer pool, and then move the test computer to that pool.
Make sure that the test computer is in the ready state before you begin your testing. If a test requires you to set parameters before you run it, a dialog box will appear for that test. For more information, review the specific test topic.
Some Windows HCK tests require user intervention. When you're running tests for a submission, it's a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting the completion of an automated test.