Skip to content

Fix #2555: Should-BeNull treats empty pipeline input as null #2689

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

Draft
nohwnd wants to merge 1 commit into
base: main
Choose a base branch
from
+18 −2

Fix #2555: Should-BeNull treats empty pipeline input as null

b6e6d64
Select commit
Loading
Failed to load commit list.
Draft

Fix #2555: Should-BeNull treats empty pipeline input as null #2689

Fix #2555: Should-BeNull treats empty pipeline input as null
b6e6d64
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Pester PR succeeded Apr 3, 2026 in 10m 25s

Build #20260403.6 succeeded

8 errors / 0 warnings

Details

Tests

  • Failed: 0 (0.00%)
  • Passed: 17,176 (98.22%)
  • Other: 312 (1.78%)
  • Total: 17,488
Code coverage

  • 6335 of 7228 line covered (87.65%)

Annotations

Check failure on line 3211 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3211 

 [-] <ScriptBlock> failed with:

Check failure on line 3211 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3211 

 [-] <ScriptBlock> failed with:

Check failure on line 3211 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3211 

 [-] <ScriptBlock> failed with:

Check failure on line 3252 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3252 

 [-] <ScriptBlock> failed with:
View more details on Azure Pipelines