Repository navigation
Add smoke tests for the native and DISM backends - #485
Merged
Merged
Conversation
The unit tests never call the native (drvstore.dll) or DISM backends, so a Windows change that breaks one of them would only show up in user reports. These tests enumerate the real driver store and check that the results make sense: oem*.inf names, an INF name and an existing folder. They don't require any packages to exist, since a clean CI machine may have none. They need Windows and an elevated process, and report Inconclusive otherwise (on Windows CI runners they run).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The unit tests never call the real backends, so a Windows change that breaks drvstore.dll or DISM would only show up in bug reports. These tests enumerate the actual driver store and check that the results make sense (oem*.inf names, an INF name, an existing folder), and that cfgmgr32 returns devices.
They don't need any third-party packages to exist, since a clean CI machine may have none. They report Inconclusive when not running elevated on Windows, so they shouldn't fail for environment reasons. They're tagged
TestCategory("Smoke")in case you want to filter them.I left PnpUtil out. On Windows Server the
pnputil /eoutput may not be in the format the parser expects, and that's a separate question.