Keyboard Testing Overview
Note This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.
The procedures that are presented in this section outline the process for testing your keyboard for correct functionality with the Microsoft Windows operating system. These procedures test your product for correct functionality by using the Microsoft Windows Driver Kit (WDK) and Driver Test Manager (DTM). To ensure full functionality, you must run all of the tests that DTM identifies as required for the device. If your product provides bus-specific support, you must run the appropriate bus-specific tests in addition to the standard tests.
Keyboard Tests
The tests that you need to run depend on the capabilities of the device or system that is being tested. To see the complete list of tests that could be required for your device, see the Keyboard Tests.
Run time: approximately one to three hours
Note You must use the latest version of the WDK to compile your driver in order for it to pass testing and obtain a logo.
Hardware Requirements
The following hardware is required for keyboard testing.
One keyboard compliant with Microsoft-specified scan codes (PS2 or HID)
If keyboard is connected through USB, one external USB 2.0 high-speed hub (unless the keyboard contains an embedded hub)
Note Testing a device to obtain a logo for Server Device qualification requires that the system being used to test the device supports four processors and a minimum of 1 GB of RAM. These system capabilities are required for the "Dynamic Partitioning (DP) Simulator and Test" and the "Multiple Processor Group" test to run. You do not need a system that actually supports DP capabilities or has greater than 64 processors to test your device.
If a pool of systems is used to test devices, at least one system in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that system must contain the device and driver being tested. As long as the driver is the same on all systems in the pool, the schedule will be created to run against all systems.
For those tests that do not include a driver to test, such as testing a hard drive, the Driver Test Manager (DTM) scheduler will constrain the DP test to run on the default system. This system should also be manually configured to have multiple processor groups. The default system is the first one listed. Test personnel, in this case, should ensure that this first system meets these minimum hardware requirements.
Note Except for Para-Virtualization drivers (as defined by Logo Requirement Policy-0020), physical devices and their associated drivers being tested for Server Logo or Signature may not be tested in virtual machines using any form of virtualization. This is because not all virtualization products support the underlying functionality needed to pass the tests relating to Multiple Processor Groups, Device Power Management, Device PCI functionality, etc.
Software Requirements
There are no additional software requirements.
Tester knowledge requirements
There are no special tester knowledge requirements.
This section includes:
Preparing for Keyboard Testing
Build date: 9/14/2012