-
Notifications
You must be signed in to change notification settings - Fork 25
Allow ordered declarations using WildcardPatternSuite #25
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
Comments
Hi jgreffe, I really appreciate that you not only created an issue, but provided a PR too! But I really wonder, why do you care about the test order in the first place? |
Hello Michael, this PR actually has two features:
This allows to have structured tests always executed in the same order so it's predictable. Not sure if it's clear enough? |
Hi again, depending on tests to be executed in a predictable order sounds like a code smell to me: Tests should be independent from each other. The best execution order (in my opinion) is: random. (Or maybe: failed first, then random) I'm still hesitant to merge your PR, because I'm not convinced that it is a good idea. On the other hand side, predictability isn't such a bad thing. ;) Would the following compromise be good enough for you: We just replace all |
Hey Michael, just pointing out this: failsafe allows Suites being ordered to give more predictability on Suite level. Would also like having the same predictability when Tests are resolved from
depending on their level in dir/package structure. But it's up to you :) |
Hello,
when I declare a suite with this, classes are randomly executed:
Maybe using LinkedHashSet would resolve this?
The text was updated successfully, but these errors were encountered: