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

Document antipattern: Running features/scenarios in a specific order #696

Open
aslakhellesoy opened this issue Nov 8, 2021 · 3 comments

Comments

@aslakhellesoy
Copy link
Contributor

See https://cucumberbdd.slack.com/archives/C60TKS3SL/p1636399065115000

I strongly recommend you avoid relying on a specific order. When a scenario fails, you should be able to run just that scenario to reproduce the same result so you can fix it. If you choose not to follow that advice, you can specify the order by listing the feature files in your runner, or as command-line arguments, depending on what Cucumber implementation you are using.

@mattwynne
Copy link
Member

Worth referencing this: http://xunitpatterns.com/Erratic%20Test.html#Lonely%20Test

@aslakhellesoy
Copy link
Contributor Author

aslakhellesoy commented Nov 8, 2021

Yes, but I'm worried about linking to sites with expired SSL certificates. That usually means unmaintained, which means it might go down.

@mattwynne
Copy link
Member

Yeah shame, that's such a useful reference site. I've contacted Gerard offline to see if he can fix his SSL certs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants