New Instructions: PowerShell Pester v5 Testing Guidelines#122
Merged
codemillmatt merged 4 commits intoJul 25, 2025
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds comprehensive PowerShell Pester v5 testing guidelines to provide GitHub Copilot with detailed instructions for generating PowerShell test files. The instructions cover test structure, assertions, mocking, data-driven testing, and best practices specific to Pester v5.
Key changes:
- Adds new instruction file for PowerShell Pester v5 testing conventions
- Updates README.md to include the new instruction in the table
- Provides detailed guidance on test structure, mocking, assertions, and configuration
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| instructions/powershell-pester-5.instructions.md | New comprehensive Pester v5 testing guidelines with examples and best practices |
| README.md | Added table entry for the new PowerShell Pester v5 instruction file |
- Introduced a new guide for PowerShell Pester testing best practices. - Covers file naming, test structure, core keywords, setup/teardown, assertions, mocking, and best practices. - Provides examples and configuration details for effective test execution.
- Removed the empty PowerShell code block from the PowerShell Pester v5 testing guidelines.
- Updated the file naming pattern from '**/*.tests.ps1' to '**/*.Tests.ps1' for consistency with PowerShell Pester v5 conventions.
3aab74f to
4cb8493
Compare
codemillmatt
approved these changes
Jul 25, 2025
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.
Pull Request Checklist
node update-readme.jsand verified thatREADME.mdis up to date.Description
Type of Contribution
Additional Notes
It references the existing
#powershell.instructions.md(as per docs: https://code.visualstudio.com/docs/copilot/copilot-customization#_custom-instructions), so works best if this is installed.By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.