Skip to content

Don't let runOrder replace JUnit orderers set elsewhere (#3529) - #3530

Merged
olamy merged 1 commit into
apache:masterfrom
olamy:issue-3529-run-order
Oct 17, 2026
Merged

olamy merged 1 commit into
apache:masterfrom
olamy:issue-3529-run-order

Conversation

@olamy

@olamy olamy commented Oct 16, 2026

Copy link
Copy Markdown
Member

Since 3.6.0, runOrder replaced any JUnit class or method orderer set in
junit-platform.properties or as a system property.

Now Surefire only sets the orderers that aren't already set.

Signed-off-by: Olivier Lamy olamy@apache.org


To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
check one of the following:

Since 3.6.0, runOrder replaced any JUnit class or method orderer set in
junit-platform.properties or as a system property.

Now Surefire only sets the orderers that aren't already set.

Signed-off-by: Olivier Lamy <olamy@apache.org>

@omatheusmesmo omatheusmesmo left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you so much @olamy , I really appreciate.

@olamy
olamy merged commit 2cdec2e into apache:master Oct 17, 2026
15 checks passed
@olamy
olamy deleted the issue-3529-run-order branch October 17, 2026 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

runOrder unconditionally overrides junit.jupiter.testclass.order.default, replacing orderers configured elsewhere

2 participants