Lightweight Filter 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 in this section outline the process for testing your NDIS Lightweight Filter driver for correct functionality with the Microsoft Windows operating system. These procedures use 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.
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.
Using the Test Procedure Help Topics
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 Windows logo testing.
Running: The running topics describe how to run the tests for your device or system.
Run time: approximately 1 hour
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.
DTM Setup for Lightweight Filter Device Testing
A DTM setup for NDIS Lightweight Filter driver testing consists of three parts: DTM Controller, DTM Studio, and DTM clients.
You can use DTM Studio to schedule the filter driver test job on the DTM clients that are registered on the DTM Controller. The following steps summarize the scheduling procedure:
Type all of the information that the filter driver test job requires into DTM Studio, and schedule the job.
Note The Lightweight filter test job requires only one DTM client machine.
DTM Studio sends job configuration information to the DTM Controller, which reserves a DTM client and dispatches the job to it.
The DTM client runs the job. It first copies NDISTest, which is the actual filter driver test tool, to the DTM client and runs NDISTest on the desktop of the current user.
After the test is finished, the log files are gathered on the DTM Controller.
This section includes the following topics:
Preparing for Lightweight Filter Driver Testing
Running the Lightweight Filter Driver Tests
Build date: 9/14/2012