Remove pinned Pester RequiredVersion causing test discovery failure#16
Merged
Marius Storhaug (MariusStorhaug) merged 3 commits intoJul 5, 2026
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix test discovery failure due to Pester version conflict
Remove pinned Pester RequiredVersion causing test discovery failure
Jul 5, 2026
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
Build, test, and publish stages will be skipped for this PR. If you believe this is incorrect, please verify that your changes are in the correct locations. |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Copilot stopped reviewing on behalf of
Marius Storhaug (MariusStorhaug) due to an error
July 5, 2026 14:24
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
This PR updates the PowerShell test file header by removing the explicit Pester module requirement, leaving only the suppression attribute at the top of the file.
Changes:
- Removed
#Requires -Modulespin to Pester5.7.1from the test file. - Removed a blank line that separated
#Requiresfrom the attribute block.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+1
to
4
| [Diagnostics.CodeAnalysis.SuppressMessageAttribute( | ||
| 'PSUseDeclaredVarsMoreThanAssignments', '', | ||
| Justification = 'Pester grouping syntax: known issue.' | ||
| )] |
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.
CI
Test-*jobs failed during Pester discovery withFileLoadException: Could not load file or assembly 'Pester, Version=5.7.1.0'... Assembly with same name is already loaded. The test file pinned an exact Pester version via#Requires, which conflicted with Pester 5.8.0 already loaded by thePSModule/Invoke-Pesteraction before discovery runs.Changes
#Requires -Modules @{ ModuleName = 'Pester'; RequiredVersion = '5.7.1' }line fromtests/PSCustomObject.Tests.ps1.The
Invoke-Pesteraction controls the Pester version centrally, so per-repo version pinning is redundant and causes this drift whenever Pester releases a new version. This aligns the test file withPSModule/Template-PSModuleand other module repos, which carry no Pester#Requirespin.