-
Notifications
You must be signed in to change notification settings - Fork 64
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
How to run specific cucumber files or tags now? #24
Comments
In development I suggest to run
As I have time will describe this somewhere in the migration docs. |
@mucsi96 , is there a way we could pass the environment as well through CLI options instead of passing it in server.js and setup.js files of cucumber examples? |
Hi @rgeraldporter here is a link which might help you. https://github.com/cucumber/cucumber-js/blob/master/docs/cli.md#running-specific-features https://docs.cucumber.io/cucumber/api/#tag-expressions Closing this for now. |
Hi @spnraju With nightwatch api i am not able to run a specific feature file, i have also tried the cucumber CLI option but i am not able to run using nightwatch-api |
It should be |
I will add this to cucumber docs |
Documentation is updated with filtering feature files and tags |
Hi! I'm cutting over our tests from nightwatch-cucumber to nightwatch-api, but can't seem to find how you can possibly run tests for specific tags or feature files via the CLI.
start-server-and-test
doesn't support passing arguments at all, so outside of writing a script entry for every single feature file & tag we have, I don't see how to get this to work in the new setup. Innightwatch-cucumber
it was very easy to do.Expected Behavior
assuming you have something like:
Running
npm run test -- features/something.feature
or
npm run test -- -t @my-tag
Current Behavior
Error: expect: <start script name> <url> <test script name>
(throws errors from start-server-and-test as it doesn't accept any more arguments, let alone passing them along)
Possible Solution
Not sure.
start-server-and-test
has an open issue about this.Context
(see above)
But also, when developing tests its fairly typical to only run the feature files you're actually developing, right now outside of writing a custom script line I don't see how to do it.
Your Environment
Node 10.10.0, MacOS 10.13.6, used example linked from
nightwatch-cucumber
for updating the deprecated module.The text was updated successfully, but these errors were encountered: