Enforce alphabetical order of tests to increase stability#80
Merged
Conversation
Contributor
Author
|
CI check passed on this PR, see it here Without this change, CI check failed, see my PR in my fork and CI run there. |
Contributor
Author
|
I also think that it would be great to start the CI only after confirmation from repo owners, just like it's here: wildfly/jboss-ejb-client#722 Do you know how to set it? |
Contributor
Author
|
@tadamski Can you please check this PR? |
tadamski
approved these changes
Oct 9, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Surefire alphabetical order is highly used in another WF TSs as well, see for example: https://github.com/wildfly/wildfly/blob/main/testsuite/integration/basic/pom.xml#L1529