pytest-bdd
pytest-bdd copied to clipboard
pytest-dev
BDD library for the py.test runner
I want to have a testcase that is parametrized on both levels: Feature and scenario as in the example in the readme. However when I implemented it and run it,...
Putting this up to get some feedback and see how receptive people are of the idea before I spend much more time on polishing this. I'm currently using this library...
First translation was written for portuguese, according to https://cucumber.io/docs/gherkin/reference/#spoken-languages. The PR also enables the language reset during runtime.
Perhaps it is not part of pytest-bdd's "subset" of Gherkin, but adding a scenario description causes issues. Here's a scenario that has a scenario description: ```gherkin Scenario: Do a thing...
I wanted to write a scenario outline like so: ``` Scenario Outline: Assemble order - delivery types Given An order has been placed And the customer has chosen delivery When...
User can parametrize scenario by using examples specified in feature files. In that case pytest `parametrize` marker is updated with examples parameters. We also provide a way to parametrize scenario...
Related to: https://github.com/pytest-dev/pytest-bdd/issues/247 https://github.com/pytest-dev/pytest-bdd/issues/235 This pull request updates `--gherkin-terminal-reporter-expanded` to enable gherkin output. Thanks to that it can be used without adding `--gherkin-terminal-reporter` to the command. This is the way...
This happened for pytest-bdd test steps. They have been renamed to avoid that: https://github.com/pytest-dev/pytest-bdd/pull/292
pytest-bdd steps in files with names that don't match pytest's patterns in the`python_files` settings, like steps.py, given.py, when.py then.py, are not picked up by pytests assertion rewriting. Here's a simple...
For me, in the documentation is not clear if I have to use `scenarios` on each step file or if I can use it in a single place once. I...
