Fix #2561: Escape control characters in assertion error messages #2690
+76
−1
Azure Pipelines / Pester PR
failed
Apr 3, 2026 in 17m 31s
Build #20260403.15 had test failures
Details
- Failed: 1 (0.01%)
- Passed: 12,931 (98.22%)
- Other: 234 (1.78%)
- Total: 13,166
- 0 of 2 line covered (0.00%)
Annotations
Check failure on line 3211 in Build log
azure-pipelines / Pester PR
Build log #L3211
[-] <ScriptBlock> failed with:
Check failure on line 3211 in Build log
azure-pipelines / Pester PR
Build log #L3211
[-] <ScriptBlock> failed with:
Check failure on line 22 in Build log
azure-pipelines / Pester PR
Build log #L22
There are one or more test failures detected in result files. Detailed summary of published test results can be viewed in the Tests tab.
Check failure on line 3252 in Build log
azure-pipelines / Pester PR
Build log #L3252
[-] <ScriptBlock> failed with:
azure-pipelines / Pester PR
Should-BeFasterThan.Has Because parameter("1ms", Start-Sleep -Milliseconds 10 ,"I said so")
Exception: Expected the script block { $Actual | Should-BeFasterThan -Expected $Expected -Because $Because } to fail in Pester assertion, but no assertion failure error was thrown!
Raw output
at Verify-AssertionFailed, D:\a\1\s\tst\axiom\Verify-AssertionFailed.ps1:26
at <ScriptBlock>, D:\a\1\s\tst\functions\assert\Time\Should-BeFasterThan.Tests.ps1:54
Loading