Skip to content
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 organize and execute a large number of features #18

Closed
hzy00 opened this issue Jan 29, 2016 · 3 comments
Closed

how to organize and execute a large number of features #18

hzy00 opened this issue Jan 29, 2016 · 3 comments

Comments

@hzy00
Copy link

hzy00 commented Jan 29, 2016

My application has many modules. So I want to orgnize my features by module in subdirectory. But, there is a problem has been harassing me:
how to execute the featues in my prefered order? Should I rename my features file in order? However, mayber I just want to execute some modules' features. I may have many different prefered order.
Maybe, someone suggests to execute featutre like this:
"cucumber -r features 1.feature 2.feature..."
That's good if my features are not too many. When I have a large number features to execute, it's to inconvenient. Anybody has better suggestion?

@yigithanyilmaz
Copy link

Hey there,

You should not execute your tests from feature files it is far from practicle. You start using tags. This will help you organize your tests freely. Add a tag to the top of your Feature file like @billing or @Important.

Cheers

Eg.
cucumber --tags @billing            # Runs both scenarios
cucumber --tags @important          # Runs the first scenario
cucumber --tags ~@important         # Runs the second scenario (Scenarios without @important)
cucumber --tags @billing --tags @important    # Runs the first scenario (Scenarios with @important AND @billing)
cucumber --tags @billing,@important           # Runs both scenarios (Scenarios with @important OR @billing)

@aslakhellesoy
Copy link
Contributor

Please use the support forums for questions and discussions. We use GitHub issues to track bugs and contributions exclusively.

@lock
Copy link

lock bot commented Oct 25, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants