CODEWITHSUNDEEP
junitcucumbercucumber-jvmcucumber-java
Steerpike
Steerpike

Reputation: 1843

Unable to glue Cucumber Features to Step definitions

Given the following maven folder structure, for which super-flights-acceptanctests is a child of a parent module, and the following Junit runner class, what is the correct configuration? Currently any maven goal I try and use to run the tests fails to find the stepdefs and prints the stub code to the console.

enter image description here

I'm pretty sure I have either the file naming conventions wrong or, more likely, the paths to the glue or features wrong in the @CucumberOptions

Upvotes: 2

Views: 7289

Answers (3)

kripindas
kripindas

Reputation: 480

From the screenshot you have provided, you are using the definition files BookStepDefs,CostStepDefs,SearchStepDefs.

For using the three definition files you have to specify the path of three definition files in the glue option because you have kept the definition files in different path.

So the glue option should be,

glue={"src/test/java/net/superair/flights/tests/book", "src/test/java/net/superair/flights/tests/cost", "src/test/java/net/superair/flights/tests/search"}

Upvotes: 1

Steerpike
Steerpike

Reputation: 1843

glue needs package naming structure - sorted

Upvotes: 0

Grasshopper
Grasshopper

Reputation: 9058

Try using glue value as "net.superair.flights.tests" in cucumberoptions

Upvotes: 4

Related Questions