Add Pester CI Analysis Skill#26806
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request adds comprehensive Pester test failure analysis capabilities to the repository, including documentation, automation scripts, and guidance materials to help developers troubleshoot failing tests in CI.
Changes:
- Adds a new "analyze-pester-failures" skill with complete documentation and a 6-step automated workflow
- Creates an automation script to systematically analyze PR test failures by fetching test results, parsing errors, and generating recommendations
- Provides reference documentation for understanding Pester stack trace formats and debugging parsing issues
- Adds instructional guidance on Pester test statuses and what constitutes a "working" test
- Updates .gitignore to exclude analysis output directories
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| .gitignore | Adds pattern to ignore pester-analysis-* directories generated by the analysis script |
| .github/skills/analyze-pester-failures/scripts/analyze-pr-test-failures.ps1 | New automated script that performs systematic 6-step analysis of Pester test failures in GitHub PRs |
| .github/skills/analyze-pester-failures/references/stack-trace-parsing.md | Reference documentation explaining Pester stack trace formats and regex parsing patterns |
| .github/skills/analyze-pester-failures/SKILL.md | Main skill documentation defining the analysis workflow and troubleshooting approaches |
| .github/instructions/pester-test-status-and-working-meaning.instructions.md | Instruction file clarifying Pester test statuses and defining what makes a test "working" |
… adjust step numbering
daxian-dbw
approved these changes
Feb 13, 2026
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.
PR Summary
This pull request adds comprehensive documentation to clarify Pester test outcomes and improve troubleshooting for test failures. The main changes include a new guide detailing the meaning of each Pester test status and best practices for writing "working" tests, as well as a reference for parsing stack traces and debugging regex extraction issues.
Pester Test Status Documentation:
.github/instructions/pester-test-status-and-working-meaning.instructions.mdwith detailed explanations of Pester test statuses (Passed,Failed,Error,Pending,Skipped,Ignored), what constitutes a "working" test, pitfalls of pending tests, recommended testing patterns, and a checklist for validating tests.Stack Trace Parsing Reference:
.github/skills/analyze-pester-failures/references/stack-trace-parsing.mddescribing supported stack trace formats, regex patterns for extracting file and line information, troubleshooting common parsing failures, and guidelines for adding new output formats to the parser.PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright header