Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Assume that we have a usermode app and multiple corresponding driver files, and we want to test our drivers against multiple builds of Windows (builds of 10,11).
By test I mean for example running the verifier against all of the drivers, and possibly also do a reboot of the machine to make sure it boots up and doesn't cause a BSOD, etc. So the goal is to find bugs like BSODs, kernel memory/handle leaks, etc.
This kinda sounds similar to HLK, but those tests are pretty much useless for software drivers based on my experience. (only 2 simple test available for most of the software drivers)
So what are the possible solutions as of 2023 for this scenario? Meaning automatic testing of our drivers after every build and checking if the build passes certain tests (like verifier), in multiple VMs that consist of different builds/versions of Windows, to catch bugs such as BSODs, memory leak, etc?
How do you guys handle this and what tests do you use to make sure your newest builds of drivers don't have a bug?
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Internals & Software Drivers||19-23 June 2023||Live, Online|
|Writing WDF Drivers||10-14 July 2023||Live, Online|
|Kernel Debugging||16-20 October 2023||Live, Online|
|Developing Minifilters||13-17 November 2023||Live, Online|