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
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. |
Got it. Thanks! 😸 |
https://jkotests.wordpress.com/2013/08/22/specify-execution-order-of-cucumber-features/ |
@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. |
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. |
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. |
Hello, @jbpros!
I read docs, but not found something about order run.
Can I specify the order of feature execution with global patterns?
I mean run
@first
test and then run other tests.Does it possible?
The text was updated successfully, but these errors were encountered: