Can't find my stepDefinitions
See original GitHub issueSince the 2.0.1 version I can’t run my tests anymore. I read the changelog and I added the required config to my package.json:
{
"nonGlobalStepDefinitions": true,
+ "stepDefinitions": "cypress/e2e",
+ "commonPath": "cypress/e2e/common"
}
(instead of being in cypress/integration
, my tests are in cypress/e2e
)
This doesn’t work. Am I reading something wrong from the documentation?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Cucumber: Unable to find step definition - Stack Overflow
It looks like Cucumber isn't finding your step defintion class. In your unit test class you say: glue = {"com.macro.definition"}.
Read more >FAQ - Cucumber Documentation
If Cucumber is telling you that your steps are undefined, when you have defined step definitions, this means that Cucumber cannot find your...
Read more >Why is my Feature File failing to find the Step Definition?
Your java is defined as a folder and not package try defining it as package and calling java.uk.co... if you see the folder...
Read more >Cucumber not finding Step Definitions Java Eclipse
Solution 1: Convert to cucumber project. Step 1: Right click on eclipse project go to Configure -> Convert to cucumber project · Solution...
Read more >Gherkin support can't find step definitions : IDEA-280423
I have a project using gherkin that used to work fine up until a few months ago. When I open it now I...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I guess the message should say “if things don’t work you need to configure the stepDefinitions”, but, also, I’m not sure how setting the stepDefinitions to a correct path could break anything? My thinking was that it’s better if anyone just explicitly set the path to the stepDefinitions, instead of relying on defaults from Cypress (that we don’t control)
Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I’m very excited about. Furthermore, I’d like to thank @lgandecki ++ for all the work that they’ve done so far.
Read more about the transfer of ownership here.
The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.