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
Add ability to use custom labels in SpecFlow plugin (#284)
* add parsing custom label as key-value
* Add new unit test to check custom label
* fix label regex
Co-authored-by: Aleksandr Kulakov <a.kulakov@dodopizza.com>
Copy file name to clipboardExpand all lines: Allure.SpecFlowPlugin/README.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,6 +111,20 @@ Scenario: ....
111
111
```
112
112
will set current scenario severity in Allure report as Blocker
113
113
114
+
#### Label
115
+
You can add Label for your scenarios using tags. It can be configured in `allureConfig.json`
116
+
```json
117
+
"labels": {
118
+
"label": "^label:([\\w]+):(.+)"
119
+
},
120
+
```
121
+
The following scenario
122
+
```cucumber
123
+
@label:layer:e2e: @label:as_id:123
124
+
Scenario: ....
125
+
```
126
+
will set current scenario Layer as e2e and Id as 123 in Allure report
127
+
114
128
#### Tables conversion
115
129
Table arguments in SpecFlow steps can be converted either to step csv-attacments or step parameters in the Allure report. The conversion is configurable in `specflow:stepArguments` config section.
116
130
With `specflow:stepArguments:convertToParameters` set to `true` the following table arguments will be represented as parameters:
0 commit comments