Skip to main content
Version: v4

Find-GherkinStep

SYNOPSIS#

Find a step implmentation that matches a given step

SYNTAX#

Find-GherkinStep [[-Step] <String>] [[-BasePath] <String>] [<CommonParameters>]

DESCRIPTION#

Searches the *.Steps.ps1 files in the BasePath (current working directory, by default) Returns the step(s) that match

EXAMPLES#

EXAMPLE 1#

Find-GherkinStep -Step 'And the module is imported'
Step                       Source                      Implementation----                       ------                      --------------And the module is imported .\module.Steps.ps1: line 39 ...

PARAMETERS#

-Step#

The text from feature file

Type: StringParameter Sets: (All)Aliases:
Required: FalsePosition: 1Default value: NoneAccept pipeline input: FalseAccept wildcard characters: False

-BasePath#

The path to search for step implementations.

Type: StringParameter Sets: (All)Aliases:
Required: FalsePosition: 2Default value: $PwdAccept pipeline input: FalseAccept 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#

RELATED LINKS#

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.