Share via

File System Testing Prerequisites

  • Article

This section describes the tasks that you must complete before you test an audio device by using the Windows Hardware Lab Kit (Windows HLK):

  • Review the hardware requirements.

  • Review the software requirements.

  • Configure the test computers.

Hardware requirements

The following hardware is required for File System testing.

  • One test computer running a supported operating system. This computer must include the following:

    • Windows keyboard

    • Two-button pointing device (this is optional if the test computer is a laptop with a touch pad or other input capability).

    • Color display monitor capable of at least 1024 by 768 resolution, 32-bits per pixel, 60 Hz

    • Persistent storage (typically a hard drive) with a minimum of 20 GB available.

    • A server running Windows 2008 R2 SP1 or later.

Note

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 your product, 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 product 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 HLK 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.

Note

Except for para-virtualization drivers (as defined by the WHCP Policies and Processes document), 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.

Note

  Multiple Processor Groups Setting You must set the value for the processor group size for Hardware Lab Kit testing of Windows Server 2008 R2 and later device drivers for certification. This is done by running bcdedit in an elevated command prompt window, using the /set option.

The commands for adding the group settings and restarting are as follows:

bcdedit.exe /set groupsize 2
bcdedit.exe /set groupaware on
shutdown.exe -r -t 0 -f

The commands for removing the group settings and rebooting are as follows:

bcdedit.exe /deletevalue groupsize
bcdedit.exe /deletevalue groupaware
shutdown.exe -r -t 0 -f

Note

Code Integrity Setting

The Virtualization Based Security feature (VBS) of Windows Server 2016 must be enabled using Server Manager first.

Once that has occurred, the following Registry key must be created and set:

HKLM\System\CurrentControlSet\Control\DeviceGuard
HypervisorEnforcedCodeIntegrity:REG_DWORD
0 or 1 (disabled, enabled)

Software requirements

The following software is required to run the File System tests:

  • The AV filter driver under test

    Warning

    Make sure that you install the product on the test computer before you install the Windows HLK Client.

Test system configuration

To configure the test system, follow these steps:

  1. Determine the letter assignment for each volume:

    NTFS

    g:

    CNTFS

    i:

    Fat16

    k:

    Fat32

    l:

    ExFat

    m:

    UDF

    n:

  2. On the client computer, make sure that the following volumes are present:

    • NTFS 2gb

    • ntfs compressed 2gb

    • fat16 1gb

    • Fat32 1gb

    • Exfat 1gb

    • UDF 2gb

  3. In the controller, modify the parameters on the jobs in the $\WDK Tests\Storage\Filesystems section to point to test volumes, as follows:

    • TxF2: Modify ntfs and cntfs to point to test volumes.

    • ReparsePonts: Modify NTFS and CNTFS to point to test volumes

    • Installable Filesystems filter test: Modify ntfs, cntfs, fat, fat32, exfat, and udf to point to test volumes.

    • Antivirus Installable Filesystems filter test: Modify ntfs, cntfs, fat, fat32, exfat, and udf to point to test volumes.

    • File IO test: Modify ntfs, cntfs, fat, fat32, exfat, and udf to point to test volumes.

    • Mapped File IO test: Modify ntfs, cntfs, fat, fat32, exfat, and udf to point to test volumes.

    • Object ID test: Modify ntfs, cntfs, fat, fat32, exfat, and udf to point to test volumes.

    • Oplocks test: Modify ntfs, cntfs, fat, fat32, exfat, and udf to point to test volumes.

    • Syscache test: Modify ntfs, cntfs, fat, fat32, exfat, and udf to point to test volumes.

  4. On the server, create a share that you name RDRTest.

  5. Modify the parameters in the $\WDK Tests\Leasing\SMB_OplockRDR test to point to the server name and share name.

Make sure that the test computer is in the ready state before you begin your testing. If a test requires parameters to be set before it is run, a dialog box will be displayed for that test. Review the specific test topic for more information.

Some Windows HLK tests require user intervention. When running tests for a submission, it is a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting completion of an automated test.