Skip to content

Commit 154ec50

Browse files
committed
Update names and links
1 parent 37f95e8 commit 154ec50

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ This is the simplest possible setup for Cucumber-JVM using Java with Maven.
44
There is nothing fancy like a webapp or browser testing. All this does is to
55
show you how to set up and run Cucumber!
66

7+
There is a single feature file with one scenario. The scenario has three steps,
8+
one passing, skipped and undefined. See if you can make them all pass!
9+
710
To write assertions the project comes with [AssertJ](https://assertj.github.io/doc/#assertj-core-assertions-guide)
811
included.
912

@@ -12,7 +15,7 @@ included.
1215
Git:
1316

1417
git clone https://github.com/cucumber/cucumber-jvm-starter-maven-java.git
15-
cd cucumber-java-skeleton
18+
cd cucumber-jvm-starter-maven-java
1619

1720
Or [download a zip](https://github.com/cucumber/cucumber-jvm-starter-maven-java/archive/main.zip) file.
1821

@@ -70,7 +73,7 @@ mvn verify -DexcludedGroups="Haricots" -Dgroups="Zucchini | Gherkin"
7073

7174
### Running a single scenario or feature
7275

73-
Maven and Gradle do not (yet) support selecting single features or scenarios
76+
Maven does not (yet) support selecting single features or scenarios
7477
with JUnit selectors. As a work around the `cucumber.features` property can be
7578
used. Because this property will cause Cucumber to ignore any other selectors
7679
from JUnit it is prudent to only execute the Cucumber engine.

0 commit comments

Comments
 (0)