Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Add Reasons to Block and Test Results #2607

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Auto stash before rebase of "reasons" onto "upstream/main"

75df833
Select commit
Loading
Failed to load commit list.
Draft

WIP: Add Reasons to Block and Test Results #2607

Auto stash before rebase of "reasons" onto "upstream/main"
75df833
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Pester PR failed Jan 9, 2025 in 12m 2s

Build #20250109.3 had test failures

35 errors / 7 warnings

Details

Tests

  • Failed: 21 (0.14%)
  • Passed: 14,664 (98.22%)
  • Other: 245 (1.64%)
  • Total: 14,930

Annotations

Check failure on line 4511 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L4511 

 [-] Testing module help.Function Context.All static parameters have description 9ms (8ms|1ms)

Check failure on line 4515 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L4515 

 [-] Testing module help.Function Describe.All static parameters have description 8ms (6ms|1ms)

Check failure on line 4534 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L4534 

 [-] Testing Set-ItResult.Set-ItResult appends the -Because reason to the message 6ms (5ms|1ms)

Check failure on line 4609 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L4609 

PowerShell exited with code '1'.

Check failure on line 1 in Testing module help.Function Context.All static parameters have description

See this annotation in the file changed.

@azure-pipelines 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
at <ScriptBlock>, /home/vsts/work/1/s/tst/Help.Tests.ps1:57

Check failure on line 1 in Testing module help.Function Describe.All static parameters have description

See this annotation in the file changed.

@azure-pipelines 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
at <ScriptBlock>, /home/vsts/work/1/s/tst/Help.Tests.ps1:57

Check failure on line 1 in Testing module help.Function Context.All static parameters have description

See this annotation in the file changed.

@azure-pipelines 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 @(), /Users/runner/work/1/s/tst/Help.Tests.ps1:57
at <ScriptBlock>, /Users/runner/work/1/s/tst/Help.Tests.ps1:57

Check failure on line 1 in Testing Set-ItResult.Set-ItResult appends the -Because reason to the message

See this annotation in the file changed.

@azure-pipelines 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
at <ScriptBlock>, /home/vsts/work/1/s/tst/functions/Set-ItResult.Tests.ps1:27
View more details on Azure Pipelines