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
A typical way to run a single Cucumber test from the command line is to use a
filter. The Cucumber Engine already supported `cucumber.filter.tags` but did
not yet support `cucumber.filter.name`.
This filter can be used in `junit-platform.properties`, the CLI (e.g.
`mvn test -Dcucumber.filter.name="^Hello (World|Cucumber)$"` and in any way
properties can be used with the JUnit Platform.
Copy file name to clipboardExpand all lines: junit-platform-engine/README.md
+18-14
Original file line number
Diff line number
Diff line change
@@ -170,49 +170,53 @@ Note: The `@` is not included.
170
170
## Configuration Options ##
171
171
172
172
Cucumber receives its configuration from the JUnit platform. To see how these
173
-
can be supplied see the JUnit documentation [4.5. Configuration Parameters](https://junit.org/junit5/docs/current/user-guide/#running-tests-config-params).
173
+
can be supplied; see the JUnit documentation [4.5. Configuration Parameters](https://junit.org/junit5/docs/current/user-guide/#running-tests-config-params).
174
174
For documentation see [Constants](src/main/java/io/cucumber/junit/platform/engine/Constants.java).
175
175
176
176
```
177
177
cucumber.ansi-colors.disabled= # true or false. default: false
178
178
179
+
cucumber.filter.name= # a regular expression
180
+
# only scenarios with matching names are executed.
181
+
# example: ^Hello (World|Cucumber)$
182
+
179
183
cucumber.filter.tags= # a cucumber tag expression.
180
-
# only matching scenarios are executed.
181
-
# example: @integration and not @disabled
182
-
184
+
# only scenarios with matching tags are executed.
185
+
# example: @Cucumber and not (@Gherkin or @Zucchini)
0 commit comments