-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feature paths of cucumber.js would not be overridden if provide particular feature file in CLI #2253
Comments
Thanks for raising @aaronpliu. This was discussed a bit in #1712 but fizzled out because the use case was solved another way. I think there are three ways we could tackle this:
The more I think about it, the more I think 3 makes the most sense. |
+1 this would be a nice addition i frequently want to run a single test (eg. while fixing a bug) ... and so i run the following expecting it to run just 1 feature npm run tests -- test/features/products.feature instead it runs the whole lot |
For running only one or some tests, I use some of these options:
|
A quick update on this: I think the best approach will be to announce our intention to make this change (see #3 from my earlier comment) by emitting a deprecation warning if you provide path(s) on the CLI that are merged into config. We can see if there is any pushback from the community with genuine use cases for having it merge instead of overwrite. (Also thanks @aleksdobrev, some smart workarounds there.) |
In cucumber.js, it looks for feature file from /features and step definitions.
Now I configured "paths" in cucumber.js with test/features/**/*feature. If provided a particular feature file in CLI, it will not be overridden "paths". Then I cannot run single feature file.
I need an alternative approach to run single or all features.
Is there any good ideas?
Cucumber version: v8.10.0
Thanks
The text was updated successfully, but these errors were encountered: