Blog

We can have Behave-Step parameters within the step names.

Behave step Parameters use matcher (name)

Modify the parameter matcher in parsing the step text. There are multiple in-built parsers present in Behave, as explained below −

• parse − It gives an easy parser that restores regular expression for the step parameters with plain syntax. For example, {parameter: type}. It allows type conversion with type converters.
• cfparse − It has the Cardinality Field (CF) support. It can support the below parse expressions −{values:Type+} – Cardinality=1..N, many{values:Type*} – Cardinality=0..N, many0{values:Type?} – Cardinality=0..1, optionalIt allows type conversion with type converters.
• re − It utilises the complete regular expressions to parse the clause. We have to take the help of the named groups (? P<name>…) to declare variables obtained from the text and then feed it to the step ().

We can have our customized matcher along with new data types with the help of the register_type method.

behave.register_type(w)

Registers a user-defined type for parsing during type conversion at the time of step matching.

class behave.matchers.Matcher(func, pattern ,step_type=None)

It extracts the parameters out of step names.

class behave.model_core.Argument(start, end, original, value, name=Name)

The attributes are as follows −

class behave.matchers.Match(func, arguments=None)

A step in the feature file is parameter decorator parameters.

The attributes are as follows −

Next Topic – Click Here