Sha256: 16fa9aea65ad2f19f54def9fc7d03480ca07092d480d9b4d8226c718e934240d
Contents?: true
Size: 1.76 KB
Versions: 9
Compression:
Stored size: 1.76 KB
Contents
@announce
Feature: Publish results
Background:
Given I set the environment variables to:
| variable | value |
| CUCUMBER_PRO_TOKEN | valid-token |
Scenario: A couple of scenarios
Given a git repo
And a feature "features/test.feature" with:
"""
Feature:
Scenario:
Given passing
Scenario:
Given failing
"""
When I run `cucumber -f Cucumber::Pro -o /dev/null -f pretty`
Then the results service should receive a header
And the results service should receive these test-step results:
| status | path | location |
| passed | features/test.feature | 3 |
| failed | features/test.feature | 6 |
And the results service should receive these test-case results:
| status | path | location |
| passed | features/test.feature | 2 |
| failed | features/test.feature | 5 |
And the stderr should not contain anything
Scenario: A scenario outline
Note that we don't specify how step results will be published. This is because it's hard to get
a location for steps when a scenario outline executes.
Given a git repo
And a feature "features/test.feature" with:
"""
Feature:
Scenario Outline:
Given <result>
Examples:
| result |
| passing |
| failing |
"""
When I run `cucumber -f Cucumber::Pro -o /dev/null -f pretty`
Then the results service should receive a header
And the results service should receive these test-case results:
| status | path | location |
| passed | features/test.feature | 7 |
| failed | features/test.feature | 8 |
Version data entries
9 entries across 9 versions & 1 rubygems