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

Features order #760

Closed
epszaw opened this issue Feb 16, 2017 · 6 comments
Closed

Features order #760

epszaw opened this issue Feb 16, 2017 · 6 comments

Comments

@epszaw
Copy link
Member

epszaw commented Feb 16, 2017

Hello, @jbpros!
I read docs, but not found something about order run.
Can I specify the order of feature execution with global patterns?

cucumber --tags @first features/**/*

I mean run @first test and then run other tests.
Does it possible?

@aslakhellesoy
Copy link
Contributor

Enforcing a particular order is something we discourage because it makes it impossible to run interdependent scenarios in isolation (which you need to do when you fix failing ones).

For this reason Cucumber will never help you run scenarios in a particular order.

Instead you should make sure they can run in any order.

@epszaw
Copy link
Member Author

epszaw commented Feb 18, 2017

Got it. Thanks! 😸

@kidwm
Copy link

kidwm commented Jul 5, 2017

https://jkotests.wordpress.com/2013/08/22/specify-execution-order-of-cucumber-features/
How about support in this way like ruby version?

@NaveenKVN
Copy link

@aslakhellesoy but its still ok to keep some possibility to execute in order rite, lets the users decide whether to use it or not. for eg, If i need to execute a step to generate some test data say a booking id before editing or cancelling the booking it will be useful. Appreciate if you could consider this.

@chuan-qin
Copy link

Really appreciate if there is some options to set, to make sure all scenarios are running in their written order inside each individual feature file.

@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

5 participants