Fix discovery tests due to trace change#1458
Merged
SteveL-MSFT merged 2 commits intoPowerShell:mainfrom Apr 2, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates DSC resource discovery Pester tests to align with recent trace-level behavior changes (invalid semver now logs at INFO instead of WARN), ensuring the discovery suite stays in sync with the CLI’s logging output.
Changes:
- Run discovery with
-l infosoINFO-level trace output is emitted during the test. - Update the invalid-semver assertion to match
INFO.*invalid semantic versionin the captured stderr log.
tgauth
approved these changes
Apr 2, 2026
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.
PR Summary
After merging both the change of version typing and not failing discovery, there seems to be a bad merge so that the test was out of date. The change from previous PR is that the trace is an INFO not a WARN, so test needed to be updated.