Closed eyalkoren closed 3 years ago
Can you elaborate a bit on how it changes the current behavior ? As far as I remember, it relies more on classpath than actual folder location, not sure if that makes any difference here.
Also, changing the location requires to also move:
specs
packagespecs.GrpcCucumberTest
will have to be moved otherwise it won't be able to read relevant specs and common steps definitions.As far as I remember, it relies more on classpath than actual folder location, not sure if that makes any difference here.
No, it looks in a path that matches the package, otherwise I wouldn't have done it. I believe the resources
folder is added to the test classpath in its entirety.
Also, changing the location requires to also move: common step definitions in specs package
This is the reason I had to do that - I started by moving the code because it is mixed with the JSON specs, then the tests didn't find the gherkin scripts. When I have code that uses a new dependency (like cucumber), it's usually a good indication for me that at least some modularization makes sense, so a dedicated package is one option.
Anyway, let's drop that, I'll just leave everything in the original package/folder for now.
I want to move the cucumber code to a separate package, but Cucumber searches the scripts based on the directory, so I am editing this as well