All 6 comments
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.
aslakhellesoy
on 18 Feb 2017
Got it. Thanks! :smile_cat:
lamartire
on 18 Feb 2017
https://jkotests.wordpress.com/2013/08/22/specify-execution-order-of-cucumber-features/
How about support in this way like ruby version?
kidwm
on 5 Jul 2017
@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.
NaveenKVN
on 20 Jul 2017
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.
chuan-qin
on 14 Aug 2017
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[bot] picture](https://avatars.githubusercontent.com/in/6672?v=4&s=40)
lock[bot]
on 25 Oct 2018
Related issues
Niceplace
路
4Comments
jan-molak
路
4Comments
igniteram
路
7Comments
zanona
路
4Comments
pellekrogholt
路
3Comments
Most helpful comment
@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.