Device.Fundamentals Reliability Testing Prerequisites
This content applies to a subset of the Windows Hardware Certification Kit (Windows HCK) Device.Device Fundamentals tests that are known as Device Fundamentals Reliability tests. (The applicable test names begin with “DF – “.)
This topic describes configuration requirements for the Windows HCK Device Fundamentals Reliability tests.
In this article:
Device Fundamentals Reliability tests require devices to be configured properly for the tests to test I/O on devices when they run. Tests log device configuration errors if devices are not configured properly.
These tests use WDTF Simple I/O interfaces to test I/O in devices. Simple I/O plug-ins are extensions to the Windows Driver Test Framework (WDTF) that implement generic device-specific I/O functionality. Before you run any tests, review the specific plug-in requirements for the device. For more information, see Provided WDTF Simple I/O plug-ins.
When you test a Bluetooth mouse, you must keep the mouse moving during the entire course of testing so that the HID mouse devnode stays enumerated the whole time. Otherwise, the Device Fundamentals Reliability tests will log failures. We recommend that you use custom/simple automatic solutions to keep the mouse moving during the tests.
The network test configuration that is required to run Device Fundamentals Reliability tests for network LAN adapters is different from the network test configuration that is required to run Device.Network Testing tests.
If the device under test (DUT) is a network LAN adapter, make sure that the network LAN adapter has an IPv6 gateway address assigned to it before you run Device Fundamentals Reliability tests.
If the test network environment cannot support a test adapter that has an assigned IPv6 gateway address (for example, if you are testing in a private network configuration or in a network configuration that supports IPv4 gateway assignments only), we recommend that you use the following test configuration:
Select a remote client or server system that is running Windows® 7 or later version of Windows.
Use an Ethernet cable to make a direction connection between the test system’s adapter to the remote system’s LAN adapter.
On the remote system, from the Network and Sharing Center, turn on file and printer sharing. (For more information about how to enable file and printer sharing, see Enable file and printer sharing.)
On the remote system, open a command prompt window that has administrative privileges. Type ipconfig /all and make a note of the IPv6 address that is assigned to the remote system’s LAN adapter.
From the command prompt window on the test system, ping the IPv6 address that you noted in the previous step. Use the ping –s option to specify the IPv6 address of the test adapter as the source address.
Provide the noted IPv6 address, without the scope ID (for example, fe80::205:ddff:fe27:3840), as the WDTFREMOTESYSTEM parameter to Device Fundamentals Reliability tests.
We strongly recommend that you complete all Device Fundamentals Reliability tests before you start to run storage tests. This means scheduling the tests two times, as follows:
Schedule the tests to run one time, to run all Device Fundamentals Reliability tests.
Schedule the tests to run one time, after Device Fundamentals Reliability tests finish running, to run Storage tests.
Storage tests reconfigure a test device and can leave the device in a state that cannot support Device Fundamentals Reliability tests. If you must run storage tests before you run Device Fundamentals Reliability tests, you must reconfigure the devices according to the preceding general requirements before you run Device Fundamentals Reliability tests.
If you are testing a media card reader or a multi-function device that has an external storage capability, you must populate all media slots of the storage device with media, according to the Volume I/O plug-in requirements.
Because of Windows HCK and test limitations, you must insert media into all media slots on the test computer also (even if you are not testing media slots on the test computer).
The Microsoft USB Test Tool (MUTT) device and the software package gives you a powerful set of tools for testing interoperability of your USB hardware with the Microsoft USB driver stack. See Test with Microsoft USB Test Tool (MUTT) for a brief overview of the different types of MUTT devices, the tests you can run by using the device, and suggests topologies for controller, hub, device, and BIOS/UEFI testing.