| 1 |
Feature: Help Formatter |
| 2 |
|
| 3 |
As a tester |
| 4 |
I want to know which formatter are supported |
| 5 |
To be able to select one. |
| 6 |
|
| 7 |
Scenario: |
| 8 |
Given a new working directory |
| 9 |
When I run "behave --format=help" |
| 10 |
Then it should pass |
| 11 |
And the command output should contain: |
| 12 |
""" |
| 13 |
Available formatters: |
| 14 |
json JSON dump of test run |
| 15 |
json.pretty JSON dump of test run (human readable) |
| 16 |
null Provides formatter that does not output anything. |
| 17 |
plain Very basic formatter with maximum compatibility |
| 18 |
pretty Standard colourised pretty formatter |
| 19 |
progress Shows dotted progress for each executed scenario. |
| 20 |
progress2 Shows dotted progress for each executed step. |
| 21 |
progress3 Shows detailed progress for each step of a scenario. |
| 22 |
rerun Emits scenario file locations of failing scenarios |
| 23 |
sphinx.steps Generate sphinx-based documentation for step definitions. |
| 24 |
steps Shows step definitions (step implementations). |
| 25 |
steps.catalog Shows non-technical documentation for step definitions. |
| 26 |
steps.doc Shows documentation for step definitions. |
| 27 |
steps.usage Shows how step definitions are used by steps. |
| 28 |
tags Shows tags (and how often they are used). |
| 29 |
tags.location Shows tags and the location where they are used. |
| 30 |
""" |