Changes between Version 66 and Version 67 of HLKTesting

Timestamp:

07/02/19 12:18:18 (5 years ago)

Author:

Samuli Seppänen

Comment:

--

HLKTesting

@@ -270 +270 @@
 == Static Tools Logo Test ==
 
-The [https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/6ab6df93-423c-4af6-ad48-8ea1049155ae Static Tools Logo Test] checks for the presence of a Driver Verification Log (DVL) log file as described in the [https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-driver-verification-log official MS documentation].
+The [https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/6ab6df93-423c-4af6-ad48-8ea1049155ae Static Tools Logo Test] checks for the presence of a Driver Verification Log (DVL) log file as described in the [https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-driver-verification-log official MS documentation]. The verification log does not have to come from the same ''build'' as the one you install to the HLK clients, but it almost certainly has to be based on the exact same ''source code''.
 
 Tap-windows6 buildsystem runs code analysis automatically for x64 Release builds, so build that variant as the first step. Test analysis files are under directory ''tap-windows6\src\x64\Release'' named as ''<sourcefile>.nativecodeanalysis.xml''. Results of the code analysis are not enough, as you also need to [https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-log-file-for-static-driver-verifier Creating a log file for Static Driver Verifier].