Hi, NTDEV!
Now I have to sign driver for Windows 7, so I adjusted test server and test machine, I passed tests that I need in Windows HLK (but some tests failed, so I didn’t run them to have only successfull ones).
As a result I created .hlkx file and uploaded it in Microsoft Partner Dev Center to get my driver signed by Microsoft. But on Manual Review step I got an error - “Fail. Errata ID not provided for not run tests”.
So I have several questions: what is happening on Manual Review step? Does that error means that I have to run all tests in target (even those that are failed)? I also found information that I have to complete this document and add it as supplement.
(but some tests failed, so I didn’t run them to have only successfull ones).
Well, that’s not how it works. The HLK uses your device class to determine which tests to run. You must pass ALL the tests it chooses, unless there is an errata that documents a problem in the test. The HLK should load filters for the current errata automatically. If you don’t pass some tests, then your driver is broken, and you need to fix it.
Are you ONLY looking for Windows 7? If so, why go through HLK at all? Why not just use self-signing and cross-signing, like we always have in the past?
The HLK uses your device class to determine which tests to run.
What should I do to make HLK choose tests for my driver? Do I have to upload .inf file? If so, where do I have to upload it?
So I have client on test system, I installed my driver there. So what do I have to choose on Selection tab in Windows HLK Studio on Controller?
Are you ONLY looking for Windows 7? If so, why go through HLK at all? Why not just use self-signing and cross-signing, like we always have in the past?
What should I do to make HLK choose tests for my driver? Do I have to upload .inf file?
Aren’t you already doing that? If not, how did you create an .hlkx file? How did you run tests at all?
The normal process is that the HLK server connects to the HLK client system being tested and enumerates all of its devices. It then presents you with a list and lets you choose. Note that the HLK can only test client systems running Windows 10. Does your driver run under Windows 10? If you need to test on earlier systems, you’ll need to use the HCK instead.
But here it’s written that cross-signing will be elaminated in July this year.
That’s their current story, but you’re trying to sign a driver now. Right? The process still works today.
The normal process is that the HLK server connects to the HLK client system being tested and enumerates all of its devices. It then presents you with a list and lets you choose. Note that the HLK can only test client systems running Windows 10. Does your driver run under Windows 10? If you need to test on earlier systems, you’ll need to use the HCK instead.
Can you tell me please what I should do if HCK chooses zero tests for my driver for win7?