⚙️ [Maintenance]: Require Pester 6.x in test files#3
Closed
Marius Storhaug (MariusStorhaug) wants to merge 2 commits into
Closed
⚙️ [Maintenance]: Require Pester 6.x in test files#3Marius Storhaug (MariusStorhaug) wants to merge 2 commits into
Marius Storhaug (MariusStorhaug) wants to merge 2 commits into
Conversation
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 7, 2026 15:49
View session
There was a problem hiding this comment.
Pull request overview
This PR aims to standardize test execution by adding an explicit Pester dependency requirement to all PowerShell test scripts in the repo, ensuring the tests run only with Pester 6.x and the expected module identity.
Changes:
- Added
#Requires -Modulesto each test file to require thePestermodule at>= 6.0.0. - Attempted to lock tests to the Pester 6.x major version via
MaximumVersion. - Added the Pester module
GUIDto pin module identity.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| Tests/AzureDevOps.VariableGroups/AzureDevOps.VariableGroups.Tests.ps1 | Adds a Pester #Requires directive at the top of the test file. |
| Tests/AzureDevOps.Tests.ps1 | Adds a Pester #Requires directive to the root test file. |
| Tests/AzureDevOps.Packaging/AzureDevOps.Packaging.Tests.ps1 | Adds a Pester #Requires directive for the packaging tests. |
| Tests/AzureDevOps.Common/Public/Invoke-AzureDevOpsRestMethod.Tests.ps1 | Adds a Pester #Requires directive for the public function test. |
| Tests/AzureDevOps.Common/AzureDevOps.Common.Tests.ps1 | Adds a Pester #Requires directive for the common module tests. |
| Tests/AzureDevOps.Account/Public/Add-AzureDevOpsAccount.Tests.ps1 | Adds a Pester #Requires directive for the public function test. |
| Tests/AzureDevOps.Account/AzureDevOps.Account.Tests.ps1 | Adds a Pester #Requires directive for the account module tests. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The GUID pins module identity (precise pinning), a stricter control than the lock-to-major risk appetite. Keep only the version range.
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 12, 2026 09:54
View session
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.
This module's test suite now pins to Pester 6, so the tests always run on Pester 6 and fail fast if only an older Pester is available.
Changed: Tests require Pester 6.x
Every test file now declares the Pester 6 requirement, so the suite always resolves Pester 6 and fails with a clear message if only an older Pester is present, instead of silently running on it.
Technical Details
Tests/**/*.Tests.ps1: added#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '6.0.0'; MaximumVersion = '6.*' }.