hey, I have a driver , it compiles , barely any warnings , passes driver verifier and runs smoothly (I don’t feel any change as a user of the system) Saying that I’m sure there are proper guidelines you guys at OSR follow to test your drivers , whilst I’m not asking for a step by step testing process description , I was wondering if there are any other recommended tests I should add into my testing scheme , and perhaps when it’s best to run them in the development process
Well… there’s this:
https://www.osr.com/nt-insider/2017-issue1/best-practices-for-windows-driver-developers/
(still accurate, except that checked builds are no longer available for anything anymore)
and this:
https://www.osr.com/nt-insider/2017-issue1/develop-and-test-complex-driver-code-in-user-mode/
I’m working on some test tools that I hope to release soon that will help with this - it should exercise all the PNP IOCTLs, etc. to provide some base level testing. Basically, leverage some of HLK tests, but without the HLK
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.