Skip to main content
Version: v4

Find-GherkinStep

This page was generated

Contributions are welcome in Pester v4-repo.

SYNOPSIS​

Find a step implmentation that matches a given step

SYNTAX​

Find-GherkinStep [[-Step] <string>] [[-BasePath] <string>]

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​

-BasePath​

The path to search for step implementations.

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

-Step​

The text from feature file

Type: System.String
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: 0
  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​

OUTPUTS​

NOTES​

VERSION​

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