File tree Expand file tree Collapse file tree 1 file changed +21
-0
lines changed
cucumber-junit-platform-engine Expand file tree Collapse file tree 1 file changed +21
-0
lines changed Original file line number Diff line number Diff line change @@ -144,6 +144,27 @@ tasks {
144144}
145145```
146146
147+ ### Running a single scenario or feature from the CLI
148+
149+ To select a single scenario or feature the ` cucumber.features ` property can be
150+ used. Because this property will cause Cucumber to ignore any other selectors
151+ from JUnit, it is prudent to execute only the Cucumber engine.
152+
153+ #### Maven
154+
155+ To select the scenario on line 10 of the ` example.feature ` file use:
156+
157+ ``` shell
158+ mvn test -Dsurefire.includeJUnit5Engines=cucumber -Dcucumber.plugin=pretty -Dcucumber.features=path/to/example.feature:10
159+ ```
160+
161+ Note: Add ` -Dcucumber.plugin=pretty ` to get test reports. Maven will not
162+ report on tests without a class.
163+
164+ #### Gradle
165+
166+ TODO: (Feel free to send a pull request. ;))
167+
147168## Suites with different configurations
148169
149170The JUnit Platform Suite Engine can be used to run Cucumber multiple times with
You can’t perform that action at this time.
0 commit comments