Parse all the objects dumped with `dump_object` from the result. Note: You must run the result with output to stdout enabled. For example, us

Extract tag names from tag data. Args: tag_data (List[dict]): The tag data to extract names from. Returns: set[str]: A set o

Parse the feature file and return a Feature object with its backgrounds, rules, and scenarios.

Render the string with the given context, but avoid replacing text inside angle brackets if context is missing. Args: input_stri

Stop collecting information and finalize the report. :param bool failed: Whether the step execution is failed.

Get step fixture name

Main entry point.

Generic step decorator. :param name: Step name as in the feature file. :param type_: Step type ("given", "when" or "then"). If None, this ste

Compile regex.

Serialize item's tags. :param item: json-serialized `Scenario` or `Feature`. :return: `list` of `dict` in the form of: [

Add new step report. :param step_report: New current step report. :type step_report: pytest_bdd.reporting.StepReport

Generate test code for the given filenames.

Get the caller module locals dictionary. We use sys._getframe instead of inspect.stack(0) because the latter is way slower, since it iterates ove

Get the caller module path. We use sys._getframe instead of inspect.stack(0) because the latter is way slower, since it iterates over all the

Get a feature by the filename. :param str base_path: Base feature directory. :param str filename: Filename of the feature file. :param st

Get features for given paths. :param list paths: `list` of paths (file or dirs) :return: `list` of `Feature` objects.

Generate a sequence of suitable python names out of given arbitrary string name.

Get a list of argument that are required for a function. :param func: The function to inspect. :return: A list of argument names.

Group steps by type.

Inject fixture definitions that can parse a step. We fist iterate over all the fixturedefs that can parse the step. Then we sort them by the

Parse feature files of given paths. :param paths: `list` of paths (file or dirs) :return: `list` of `tuple` in form: (`list` of

Parse a scenario data dictionary into a ScenarioTemplate object. Args: scenario_data (dict): The dictionary containing scenario d

Parse a list of step data into Step objects. Args: steps_data (List[dict]): The list of step data. Returns:

Render the scenario with the given context. Args: context (Mapping[str, Any]): The context for rendering steps. Returns:

Serialize the step execution report. :return: Serialized step execution report. :rtype: dict

Execute the scenario. :param feature: Feature. :param scenario: Scenario. :param request: request.

Execute step function.

Extract the first background from rule children if it exists.

Yield each parsed scenario under a rule.

Find step fixturedef.

Get scenario test run result. :param step: `Step` step we get result for :param report: pytest `Report` object :return: `dict

Parse a rule, including its background and scenarios, and add to the feature.

Parse an individual scenario and add it to the feature's scenarios.

Parse a feature file into a Feature object. Returns: Dict: A Gherkin document representation of the feature file.

Add a new example row. Args: values (Sequence[str]): The values for the example row.

Add a step to the scenario. Args: step (Step): The step to add.

Generate contexts for the examples. Yields: Dict[str, Any]: A dictionary mapping parameter names to their values for each example

Stop collecting information and finalize the report as failed.

Find the fixture defs that can parse a step.

Find a unique name among a set of strings. New names are generated by appending an increasing number at the end of the name. Example: >>

Get value from ini config. Return default if value has not been set. Use if the default value is dynamic. Otherwise, set default on addini call.

Get the step function (context) for the given step. We first figure out what's the step fixture name that we have to inject. Then we let `pa

Map the error message to a specific exception type and raise it.

Inject fixture into pytest fixture request. :param request: pytest fixture request :param arg: argument name :param value: ar

Match given name with the step name.

Return the parent node IDs of a given node ID, inclusive. For the node ID "testing/code/test_excinfo.py::TestFormattedExcinfo::test_repr

Make python attribute name out of a given string.

Migrate all bdd-based tests in the given test file.

Get step arguments. :return: `dict` of step arguments

Parse step arguments.

Print missing code with TerminalWriter.

Render the datatable with the given context, but avoid replacing text inside angle brackets if context is missing. Args:

Run tests in testdir and parse json output.

Set the parameter names for the examples. Args: keys (Iterable[str]): The parameter names to set.

Wrap pytest session to show missing code.

Enter pytest's pdb trace.

Check if there are any examples. Returns: bool: True if there are examples, False otherwise.

Initialize a step. Args: name (str): The name of the step. type (str): The type of the step (e.g., 'given', 'when', '

Compile parse expression.

Compile parse expression.

Step report constructor. :param pytest_bdd.parser.Step step: Step.

Scenario report constructor. :param pytest_bdd.parser.Scenario scenario: Scenario.

Return a string representation of the step. Returns: str: A string representation of the step.

The current scenario outline parametrization. This is used internally by pytest_bdd. If no outline is used, we just return an empty dict to

Preparing fixture duplicates for output.

Add pytest-bdd options.

Add pytest-bdd options.

Add a step to the background. Args: step (Step): The step to add.

Finalize the step report as successful.

Create scenario report for the item.

Store step start time.