Better output for PSScriptAnalyzer tests and use Pester foreach#187
Merged
FriedrichWeinmann merged 1 commit intoJan 10, 2024
Merged
Better output for PSScriptAnalyzer tests and use Pester foreach#187FriedrichWeinmann merged 1 commit into
FriedrichWeinmann merged 1 commit into
Conversation
Member
|
Thanks for the uplift here - definitely more useful output than the original code! |
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
2 participants
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.
Took me a while but as discussed at PSConfEU here is a updated version of the pestertest for psscriptanalyzer. I haven't added the severity tags as it didn't look usefull in this context.