Skip to main content
Version: v4

AfterEachScenario

SYNOPSIS

Defines a ScriptBlock hook to run after each scenario to set up the test environment

SYNTAX

All (Default)

AfterEachScenario [-Script] <ScriptBlock> [<CommonParameters>]

Tags

AfterEachScenario [-Tags] <String[]> [-Script] <ScriptBlock> [<CommonParameters>]

DESCRIPTION

AfterEachScenario hooks are run after each Scenario that is in (or above) the folder where the hook is defined.

This is a convenience method, provided because unlike traditional RSpec Pester, there is not a simple test script where you can put setup and clean up.

EXAMPLES

Example 1

PS C:\> {{ Add example code here }}

{{ Add example description here }}

PARAMETERS

-Tags

Optional tags. If set, this hook only runs for features with matching tags

Type: String[]
Parameter Sets: Tags
Aliases:

Required: True
Position: 1
Default value: @()
Accept pipeline input: False
Accept wildcard characters: False

-Script

The ScriptBlock to run for the hook

Type: ScriptBlock
Parameter Sets: (All)
Aliases:

Required: True
Position: 1
Default value: None
Accept pipeline input: False
Accept wildcard characters: False

CommonParameters

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

INPUTS

OUTPUTS

NOTES

https://pester.dev/docs/v4/commands/BeforeEachScenario

https://pester.dev/docs/v4/commands/BeforeEachFeature

https://pester.dev/docs/v4/commands/AfterEachFeature

EDIT THIS PAGE

This page was auto-generated using Pester's comment based help. To edit the content of this page, change the corresponding help in the pester/Pester v4 repository. See our contribution guide for more information.