Windows SideShow Testing Overview
The procedures presented in this section outline the process for testing your Windows SideShow-compatible device for proper functionality with the Microsoft Windows operating system. These procedures use the Microsoft Windows Logo Kit (WLK) and Driver Test Manager (DTM). To ensure full functionality, you must run all of the tests that the DTM identifies as required for the device. If your device provides bus-specific support (e.g. USB), the set of required tests will include the appropriate bus-specific tests in addition to the standard tests.
The test procedures in this section are divided into the following types of topics:
- Overview: The overview topics describe the hardware, software, and tester knowledge requirements.
- Preparing: The preparing topics describe how to configure the system or systems for "Designed for Windows" logo testing.
- Running: The test procedure topics describe how to run each test in the WLK using the DTM.
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.
Windows SideShow Tests
The tests that you need to run depend on the capabilities of the device or system that you are testing. To see the complete list of tests that you might need for your device, see section “Available Jobs for Windows SideShow Logo Testing” under Running the Windows SideShow Tests.
Hardware Requirements
The following hardware is required for Windows SideShow testing. You might need additional hardware if the test device provides bus-specific support. See the test description for each bus-specific test to determine if there are additional hardware requirements.
- The Windows SideShow device to test.
- Any connection or protocol-specific hardware on the computer (for example, USB cables or a Bluetooth adapter).
Note: If the device is a USB device, see USB Device Logo Testing Recommended Practices for additional hardware setup requirements. - Any hardware required by DTM (e.g. network connectivity between the DTM client machine and DTM controller machine).
- A display (such as a monitor) should be connected to the computer being used to test the device. It is required for the subset of tests which are not fully automated, as those tests will display instructions to the tester.
- Some form of keyboard and mouse input devices should be connected to the computer being used to test the device. They are required for the subset of tests which are not fully automated, as those tests may have steps which require user input from a keyboard and a mouse to complete.
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
The following software is required to run the Windows SideShow tests:
The INF file for the device driver, if not supplied with Windows.
Device drivers for Windows SideShow device, if not shipped with Windows.
DTM components installed on the computers in your lab. For more information, see Setting Up DTM.
A version of Windows which supports Windows SideShow, installed on the computer being used to test the device. This includes:****
- The following editions of Windows Vista: Home Premium, Business, Enterprise, Ultimate
- Windows 7
Note Windows SideShow support also requires Windows Media Player to be installed, so the “N” versions of Windows that ship without Windows Media Player cannot be used.
Tester Knowledge Requirements
To run the Windows Sideshow tests, testers must know how to:
- Connect or pair the Windows SideShow device to the computer.
- Install the Windows SideShow device drivers, if required.
- Use DTM Studio and Device Console to create Logo submissions and to manage test execution. Testers should be familiar with all information under section Using DTM for Logo Testing.
- To complete the subset of tests which are not fully automated:
- The tester must have physical access to both the device being tested and the computer the device is connected to or paired with.
- The tester must be able to read and follow any English instructions displayed on the computer and on the device being tested.
- The tester must be able to use the computer’s keyboard and mouse, as well as the SideShow device’s input mechanisms (such as buttons or a touchscreen), to perform the tasks instructed by the tests.
This section includes the following topics:
Preparing for Windows SideShow Testing
Running the Windows SideShow Tests
Troubleshooting Windows SideShow Testing
Send feedback on this topic
Built on December 10, 2009