Add Pester v5 support to problem matcher #2998
Merged
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 requests extends the problemMatcher pattern for Pester to support new timings printed by Pester v5+. This will enable vscode-powershell to also detect failed tests using a future release of Pester v5.
A related PR in Pester, pester/Pester#1700, is also required for this to work as it adds Pester 4-style output when tests are run in a vscode-task (not integrated terminal). This output is automatic and does not require the a special option like
IncludeVSCodeMarker
. The related PR will be released in Pester 5.1Fix #2931
PR Checklist
WIP:
to the beginning of the title and remove the prefix when the PR is ready