Skip to main content
Version: v6

Should-BeFalsy

This page was generated

Contributions are welcome in Pester-repo.

SYNOPSIS​

Compares the actual value to a boolean $false or a falsy value: 0, "", $null or @(). It converts the input value to a boolean.

SYNTAX​

Should-BeFalsy [[-Actual] <Object>] [[-Because] <string>]

DESCRIPTION​

This assertion evaluates the input using PowerShell truthiness rules. It passes for values such as $false, 0, "", $null, and empty collections.

EXAMPLES​

EXAMPLE 1​

$false | Should-BeFalsy
$null | Should-BeFalsy
$() | Should-BeFalsy
@() | Should-BeFalsy
0 | Should-BeFalsy

These assertion will pass.

EXAMPLE 2​

$true | Should-BeFalsy
Get-Process | Should-BeFalsy

These assertions will fail, because the actual value is not $false or falsy.

PARAMETERS​

-Actual​

The actual value to compare to $false.

Type: System.Object
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: 0
  IsRequired: false
  ValueFromPipeline: true
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''

-Because​

The reason why the input should be the expected value.

Type: System.String
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: 1
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''

CommonParameters​

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

INPUTS​

System.Object​

OUTPUTS​

NOTES​

The Should-BeFalsy assertion is the opposite of the Should-BeTruthy assertion.

Use the -ErrorAction parameter to control soft-assertion behavior for this assertion. -ErrorAction Continue records the failure and lets the rest of the test run (a soft assertion), while -ErrorAction Stop fails the test immediately, for example to guard a precondition before continuing.

When -ErrorAction is not specified, the behavior comes from Should.ErrorAction in the configuration, which defaults to Stop. See https://pester.dev/docs/assertions/soft-assertions for more about soft assertions.

VERSION​

This page was generated using comment-based help in Pester 6.0.0.