Clarify docs on --gherkin-terminal-reporter

This commit is contained in:
Kyle Adams 2024-08-13 10:09:14 -04:00
parent d517a80fd1
commit fcf24a42e4
No known key found for this signature in database
3 changed files with 4 additions and 2 deletions

View File

@ -19,6 +19,7 @@ These people have contributed to `pytest-bdd`, in alphabetical order:
* `Floris Bruynooghe <flub@devork.be>`_
* `Harro van der Klauw <hvdklauw@gmail.com>`_
* `Hugo van Kemenade <https://github.com/hugovk>`_
* `Kyle Adams <https://github.com/kadams54>`_
* `Laurence Rowe <l@lrowe.co.uk>`_
* `Leonardo Santagada <santagada@github.com>`_
* `Milosz Sliwinski <sliwinski-milosz>`_

View File

@ -3,6 +3,7 @@ Changelog
Unreleased
----------
- Update documentation to clarify that `--gherkin-terminal-reporter` needs to be used with `-v` or `-vv`.
7.2.0
----------

View File

@ -1054,11 +1054,11 @@ To have an output in json format:
This will output an expanded (meaning scenario outlines will be expanded to several scenarios) Cucumber format.
To enable gherkin-formatted output on terminal, use
To enable gherkin-formatted output on terminal, use `--gherkin-terminal-reporter` in conjunction with the `-v` or `-vv` options:
::
pytest --gherkin-terminal-reporter
pytest -v --gherkin-terminal-reporter
Test code generation helpers