Tips for testing drivers during development
When should you start testing? As soon as you have the requirements for your driver, you can begin to design test cases to test that the critical requirements have been implemented. Studies show that finding and fixing defects in code becomes more expensive the longer the defects remain in the code. Finding and fixing defects early in the development cycle is less costly and disruptive than finding defects after the code has been released and distributed. Creating your test cases early can also help you find problems in your design.
Use the following suggestions for testing your driver code and driver package.
To help you find bugs at compile time:
Declare your driver-supplied callback functions and dispatch routines using function-role types. This helps to improve the accuracy of the code analysis and verification tools and the effectiveness of your test time. For more information about how to declare your driver-supplied functions, see Using Function Role Type Declarations.
- Compile your code using the Level4 (/W4) Warnings option. Fixing warnings that are detected by the compiler will increase the quality of the driver code and help eliminate additional defects earlier in the development cycle.
- Annotate your code using the Microsoft source code annotation language (SAL) 2.0. The annotations describe how a function uses its parameters—the assumptions it makes about them, and the guarantees it makes when it finishes. The annotations also improve the accuracy of the code analysis tools. For more information about the driver-specific annotations, see SAL 2.0 Annotations for Drivers.
Use the tools for verifying drivers while you are developing your driver. For guidelines about when to use specific verification tools, see Analyzing a Driver using Code Analysis and Verification Tools and the Survey of Verification Tools.
To test your driver package:
Create the INF file and your driver package early in the development process and use it throughout testing.
Use the ChkINF tool to verify the structure and syntax of the INF file, and to help you diagnose the INF file and other installation related issues.
Use the Inf2Cat tool (with the /nocat option) to do additional INF file verification. Inf2Cat can verify that the files referenced by the INF are present and placed in the package directory as the INF expects them to be.
Sign drivers to facilitate the installation and testing of drivers, as described in Signing Drivers during Development and Test.
Run the DriverInstall test that is included as part of the Device Fundamental tests that are provided in the WDK. See How to test a driver at runtime using Visual Studio and How to select and configure the Device Fundamental Tests. The DriverInstall test can be run after the driver has been deployed to the test computer. You can add the DriverInstall test to a Driver Test Group. The DriverInstall test appears in the Driver Test Categories under All Tests\Basic\Device Fundamentals\DriverInstall. You can also use the IWDTFDriverPackageAction2 interface to write you own tests.
Troubleshoot device installation problems by using Device Manager to view system information about drivers and devices and by consulting the SetupAPI log. The SetupAPI log contains information about the sequence of operations that occurred during the installation of a device or driver.
Using Visual Studio and the WDK, you can test and troubleshoot driver package installation when you deploy your driver to a test computer, see Deploying a Driver to a Test Computer. Select the Install and Verify option from the Deployment Properties for Driver Package Projects. When you select this option and specify the Default Driver Package Installation Task (possible reboot) or Default Printer Driver Package Installation Task (possible reboot), the test reads the driver's INF file and installs the driver. The test then verifies that the driver is up and running. Upon completion, the test provides detailed information about the success or failure of the installation task. The results show in the Driver Test Group Explorer, under Driver Test Groups > Driver Installation. The task name is Default Driver Package Installation Task.
To test your driver at run time:
Run the Device Fundamental tests that are included in the WDK. See How to test a driver at runtime using Visual Studio and How to select and configure the Device Fundamental Tests.
- Set up a debugger so that you can troubleshoot and debug the test results. For more information, see Setting Up Kernel-Mode Debugging in Visual Studio.
- Enable Driver Verifier on the test computers you use for deployment, see Driver Verifier Properties for Driver Projects. Select the DDI Compliance checking option. If your driver fails DDI Compliance checking, run Static Driver Verifier and specify the rule or rules that caused the failure. The Static Driver Verifier can help you locate the cause of the bug in your source files.
Test your driver and device on as many different hardware configurations as you possibly can. Varying the hardware can help you find conflicts between devices and other errors in device interactions. For example, you should test your driver and device on computers that have different processor architectures and on computers that are running 32-bit and 64-bit versions of Windows.
- Test the driver and device using the Checked Build of Windows. Running your driver on the checked build of Windows (or just the checked operating system and HAL) can help you to detect errors that are not evident in testing with other tools. Running with the checked build in conjunction with a kernel debugger should be a standard part of developing and testing your driver.
Test your driver and device on multiprocessor systems. Race conditions and other timing problems appear on multiprocessor systems that would not otherwise be found. See How to select and configure the Device Fundamental Tests and Boot Parameters to Test Drivers for Multiple Processor Group Support.
Test your driver and device for specific system and hardware conditions, particularly edge conditions. For example, these conditions might include "D3 hot" and "D3 cold." Make sure your driver and device can return correctly from device power state "D3 hot" (without losing power) and "D3 cold" (when power is removed from the device). For more information, see How to select and configure the Device Fundamental Tests.
Build date: 11/16/2013