You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, allure-cucumber will analyze your cucumber tags looking for Test Management, Issue Management, and Severity hooks. Links to TMS and ISSUE and test severity will be displayed in the report. By default these prefixes are used:
33
40
34
-
```ruby
41
+
```ruby
35
42
DEFAULT_TMS_PREFIX='TMS:'
36
43
DEFAULT_ISSUE_PREFIX='ISSUE:'
37
44
DEFAULT_SEVERITY_PREFIX='SEVERITY:'
38
45
```
39
46
40
-
Example:
47
+
Example:
48
+
41
49
```gherkin
42
50
@SEVERITY:trivial @ISSUE:YZZ-100 @TMS:9901
43
51
Scenario: Leave First Name Blank
44
52
When I register an account without a first name
45
53
Then exactly (1) [validation_error] should be visible
46
-
```
54
+
```
47
55
48
56
You can configure these prefixes as well as tms and issue tracker urls like this:
Then exactly (1) [validation_error] should be visible
66
-
```
73
+
```
67
74
68
75
Additional special tags exists for setting status detail of test scenarios, allure will pick up following tags: `@flaky`, `@known` and `@muted`
69
76
@@ -75,7 +82,7 @@ Put the following in your `features/support/env.rb` file:
75
82
require'allure-cucumber'
76
83
```
77
84
78
-
Use `--format Allure::CucumberFormatter --out where/you-want-results` while running cucumber or add it to `cucumber.yml`
85
+
Use `--format AllureCucumber::CucumberFormatter --out where/you-want-results` while running cucumber or add it to `cucumber.yml`
79
86
80
87
You can also manually attach screenshots and links to test steps and test cases by interacting with allure lifecycle directly. For more info check out `allure-ruby-commons`
This adaptor only generates json files containing information about tests. See [wiki section](https://docs.qameta.io/allure/#_reporting) on how to generate report.
0 commit comments