-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot run tests by path of .feature-file #473
Comments
Yes, that's probably a bug. Currently (1.1.2) you can only override option values, and feature paths are not options. We may have to add a Also see #463. |
it would be a great "feature". it's also necessary for possibility to rerun failed scenarios (using rerun formatter) |
Please don't ask for multiple features in the same ticket. |
I debugged this and it does seem to be a bug to me as it does work when you add a line number to the System variable like so: mvn test -Dcucumber.options="src/test/resources/package/Some.feature:40" The 'if' at https://github.com/cucumber/cucumber-jvm/blob/master/core/src/main/java/cucumber/runtime/RuntimeOptions.java#L112 only gets run when a linenumber is found at https://github.com/cucumber/cucumber-jvm/blob/master/core/src/main/java/cucumber/runtime/RuntimeOptions.java#L109. Am I missing something or is this a bug afterall? |
This works in both v1.2.5 and v2.0.0-SNAPSHOT (with of without line filters on the feature path). |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
When I try to start some test by using .feature path like this:
mvn test -Dcucumber.options="src/test/resources/package/Some.feature"
cucumber-jvm starts all tests i have (all .feature-files). could it be a bug?
i'm using version 1.1.2
thx
The text was updated successfully, but these errors were encountered: