docs.rs failed to build cucumber-reporter-0.2.5
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
cucumber-reporter-0.3.0
Goal
To create a reporter for the crate cucumber, that directly produces html files.
for each execute feature an html file is produced using the name of the feature. At the end an index file is produced with all executed features and some stats.
You can use the commandline option --output-html-path to change the output path of the html files, default it uses the current directory where the tests are run.
Examples
A simple gherkin feature file
Feature: Simple feature
With a description
Scenario: Scenario 1
Given a fact
When something is executed
Then the result is oke
Scenario: Scenario 2
Given a fact
And a other fact
When something is executed
Then the result is failed
Scenario: Scenario 3
Given a fact
Then a Skipped line
Will produce the following html output

A gherkin feature file using and outline
Feature: documentation with outline
Scenario Outline: Scenario Outline name <test>
Given a fact with '<Header1>'
Given a fact with '<Header2>'
Examples:
| Header1 | Header2 | test |
| Value 1 | Value 1 | 1 |
| Value 2 | Value 2 | 2 |
| Value 3 | Value 3 | 3 |
| Value 4 | Value 4 | 4 |
Scenario Outline: Scenario with skipped
Given a skipped fact with '<Header1>'
Examples:
| Header1 | Header2 | test |
| Value 3 | Value 3 | 3 |
| Value 4 | Value 4 | 4 |

planned
- direct pdf output
- custom templating