WIP: Add Reasons to Block and Test Results #2607
Draft
Azure Pipelines / Pester PR
cancelled
Dec 11, 2025 in 8m 35s
Build #20251211.3 had test failures
Details
- Failed: 18 (0.14%)
- Passed: 12,864 (98.08%)
- Other: 234 (1.78%)
- Total: 13,116
Annotations
Check failure on line 3211 in Build log
azure-pipelines / Pester PR
Build log #L3211
[-] <ScriptBlock> failed with:
azure-pipelines / Pester PR
Testing module help.Function Context.All static parameters have description
Expected $null, but got 'Reason'.
Raw output
at $parametersMissingHelp | Should -Be @(), /home/vsts/work/1/s/tst/Help.Tests.ps1:57
azure-pipelines / Pester PR
Testing module help.Function Describe.All static parameters have description
Expected $null, but got 'Reason'.
Raw output
at $parametersMissingHelp | Should -Be @(), /home/vsts/work/1/s/tst/Help.Tests.ps1:57
azure-pipelines / Pester PR
Testing module help.Function Context.All static parameters have description
Expected $null, but got 'Reason'.
Raw output
at $parametersMissingHelp | Should -Be @(), D:\a\1\s\tst\Help.Tests.ps1:57
azure-pipelines / Pester PR
Testing Set-ItResult.Set-ItResult appends the -Because reason to the message
Expected strings to be the same, but they were different.
Expected length: 45
Actual length: 25
Strings differ at index 0.
Expected: 'is skipped, because we are forcing it to skip'
But was: 'we are forcing it to skip'
^Raw output
at $_.Exception.Message | Should -Be "is skipped, because we are forcing it to skip", /home/vsts/work/1/s/tst/functions/Set-ItResult.Tests.ps1:27
Loading