3. Customer and Partner Connections Design and Develop Assess and Certify

4. Design Implement Test Assess and Certify Customer and Partner Connection s

5. Design Implement Test Assess and Certify Customer and Partner Connection s

9. Rules

10. Verification Harness

11. Static tools DesignTest Assess and Certify Customer and Partner Connections

12. Verifies complete driver including libraries together Determines if a driver obeys OS interaction rules WDM, KMDF, NDIS & storage driver support C++ support added for Windows 8

15. Runtime tools DesignImplement Test Assess and Certify Customer and Partner Connections

17. F5 Test

20. Use Static Driver Verifier to find driver defect Deploy the test driver to test system using WDK test harness Run Device Fundamentals test to expose and crash driver Demonstration of debugger integration

23. It’s simple to select and verify OS rules applicable to your driver type.

24. Results of running SDV against the Toastmon driver. We found a bug in the driver. There is a code path where PsGetVersion() is called at an IRQL > PASSIVE_LEVEL. That’s not good.

25. Deploying a driver to a remote test machine is easy. You access these options via the project’s properties

26. Here’s how you enable and configure Driver Verifier on the test machine, without leaving your chair, or Visual Studio.

27. F5 Press F5…

28. F5 Now we press F5 … and switch to the test machine to watch your driver get installed!

29. By pressing F5 you : Build, Package/Sign, Deploy, Install and Debug your driver!

30. Create a new test group and add one of the many Device Fundamentals tests provided to you by Microsoft.

31. F5 Now we press F5 We select the Surprise Remove test from the PNP group.

32. Specify the device you’d like to target, the test parameters, and click the Run button…

33. The test was successfully run on the remote machine. Access the logs using the Test Group Explorer pane on the left

34. Let’s change one of the test parameters and try again. This time we’ll send IO to the device before surprise remove.

35. The test crashed the remote machine! The debugger automatically breaks in…

36. You’re Kernel debugging, over the network, from Visual Studio. !Analyze tells you exactly what the driver did wrong. It’s the same bug SDV caught earlier!

37. Rules

38. ToastMon_DispatchPnp ( Irp ) ToasterDrvCancelQueuedReadIrps Pnp/Io Manager KeAcquireSpinlock IoMarkIrpPending (Irp) PsGetVersion ToastMon_DispatchRead ( Irp ) InsertTailList(,&Irp->…) Return STATUS_PENDING KeAcquireSpinlock:KeAcquireSpinlock: After this call the IRQL is raised from PASSIVE to Dispatch.

39. Test

40. Create a functional test using driver test template Build and run test using Window Driver Kit

41. The WDK supplies Driver Test templates for various categories of tests.

42. With just 3 simple changes to the template, we create a functional IOCTL test for the OSRUsbFx2 device. Step 1

43. Step 2

44. Step 3

45. As soon as you Press F5 and build your new test, it shows up in the test library, ready to run!

46. Step 3 Specify the number you’d like to display on the Seven-Segment Display on the OSRUsbFx2 device…

47. Run your custom test and observe the OSRUsbFx2 device connected to the remote machine

48. Review

51. Code Analysis Static Driver Verifier Easily Run Tests Device Fundamentals Tests Driver Verifier Write Device Specific Tests Write Device Specific Tests Design Implement Test Assess and Certify Customer and Partner Connection s

52. HW-328T – Using the Windows Driver Framework to build better drivers HW-118T – Advanced app and driver debugging TOOL-100T - Improving software quality using Visual Studio 11 C++ Code Analysis RELATED SESSIONSDOCUMENTATION & ARTICLES Tools for Verifying Drivers Tools for Testing Drivers Windows Hardware Dev Center Windows Dev Center

53. HW-907C Inside the Windows 8 driver developer workflow CHALK TALKHANDS ON LAB win8wdk@microsoft.com CONTACT 721 Experiencing Windows Driver Kit integration with Visual Studio Windows Hardware Engineering Tools EXPO BOOTH