Skip to content

📖 [Docs]: Document the Pester major-version lock in the test pipeline #362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Marius Storhaug (MariusStorhaug) merged 4 commits into from
Jul 7, 2026
Merged

📖 [Docs]: Document the Pester major-version lock in the test pipeline #362

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cfb845d
Document the Pester major-version lock in the test pipeline
MariusStorhaug Jul 7, 2026
fdd5699
Use the 6.* wildcard for the Pester major-version ceiling
MariusStorhaug Jul 7, 2026
42c4e6c
Drop the GUID from the Pester requirement example
MariusStorhaug Jul 7, 2026
45b7896
Clarify the Pester requirement is a module-author convention, not pip…
MariusStorhaug Jul 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,7 @@ The [PSModule - SourceCode tests](./scripts/tests/SourceCode/PSModule/PSModule.T

[workflow](./.github/workflows/Test-ModuleLocal.yml)
- Imports and tests the module in parallel (matrix) using Pester tests from the module repository.
- Module test files declare a Pester **6.x** requirement via `#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '6.0.0'; MaximumVersion = '6.*' }` — a convention module authors add to each `*.Tests.ps1`, not something this pipeline injects. The [Invoke-Pester](https://github.com/PSModule/Invoke-Pester) action installs a matching `6.x`, so minor and patch updates flow in automatically while a new major stays a deliberate, reviewed change.
- Supports setup and teardown scripts executed via separate dedicated jobs:
- `BeforeAll`: Runs once before all test matrix jobs to set up the test environment (e.g., deploy infrastructure, download test data).
- `AfterAll`: Runs once after all test matrix jobs complete to clean up the test environment (e.g., remove test resources, clean up databases).
Expand Down