Test example params are rendered where necessary: * Step names * Docstring * Datatables

As param takes precedence even if ini config is correct it should fail if passed param is incorrect

If ini config is incorrect but param path is fine it should be able to find features

Test feature base dir.

Test parametrised scenario when the parameter contains a slash, such in a URL.

Test if the code is generated by a given feature.

Test generate missing command.

Test that step parsers are correctly discovered and won't be part of the missing steps.

Test that code generation escapes quote characters properly.

Test that @given, @when, @then just delegate the work to @step(...). This way we don't have to repeat integration tests for each step decorator.

Test when step defined in the parent conftest.

Test first step using incorrect initial keyword.

Test improper step without keyword.

Regression test for https://github.com/pytest-dev/pytest-bdd/issues/317

Correctly identify when keyword is used for steps and when it's used for other cases.

Test locally overridden fixtures.

Test if main command shows help when called without the subcommand.

Test if the code is migrated by a given file mask.

Test misplaced or incorrectly formatted Rule.

Test misplaced or incorrect Scenario keywords.

Test multilanguage support.

Test multiple backgrounds in a single feature.

Test multiple features in a single feature file.

Test validation error when multiple features are placed in a single file.

Using the same given fixture raises an error.

Test no scenarios defined in the feature file.

Test parametrized feature example table with escaped pipe characters in input.

Test outlined scenario also using other parametrized fixture.

Test parent given is collected. Both fixtures come from the parent conftest.

Regression test for https://github.com/pytest-dev/pytest-bdd/pull/577

Simulate a plugin forcing an exit during configuration before bdd is configured https://github.com/pytest-dev/pytest-bdd/issues/362

Test python name generator function.

Parser correctly handles steps that are not left-aligned

Test that aliases for various keywords are accepted and reported correctly. see https://cucumber.io/docs/gherkin/reference/

Test comments inside scenario.

Test scenario function is used not as decorator.

Test the situation when scenario is not found.

Test scenarios shortcut (used together with @scenario for individual test override).

Test scenarios shortcut when no scenarios found.

Test scenario decorator with a standard usage.

Test that the @step(...) decorator works for all kind of steps.

Issue 173: Ensure step definitions are found when using pytest.main.

When step fails.

Test step outside of a Scenario or Background.

Test that if the step parser defines an argument, but step function does not accept it, then it does not fail and the params is just not filled.

Test step trace.

Test step trace.

Test step trace.

Test that steps definition containing a yield statement work the same way as pytest fixture do, that is the code after the yield is executed durin

Test that normal steps don't take precedence over the other steps.

Make sure using a tag after background works.

Test tests selection by tags.

Test generating code with unicode characters. Primary purpose is to ensure compatibility with Python2.

Test parametrized scenario when the test function lacks parameters.

Test advanced use cases, like the implementation of custom step generators.

Test regression found in issue #524, where we couldn't find the correct step implemntation in the hierarchy of files/folder as expected.

Test example parameter name and step arg do not redefine each other's value if the same name is used for both in different steps.

Then step decorator. :param name: Step name or a parser object. :param converters: Optional `dict` of the argument or parameter converters in

When step decorator. :param name: Step name or a parser object. :param converters: Optional `dict` of the argument or parameter converters in