TestMethodOrder not respected under concurrent execution

TestMethodOrder not respected under concurrent execution

When enabling parallel test execution in JUnit 5 with @Execution(ExecutionMode.CONCURRENT), the ordering specified by @TestMethodOrder appears to be ignored, causing interleaved test runs that break assumptions about state initialization.

The goal is to understand whether the ordering guarantee holds when tests are scheduled on multiple threads, and if not, what mechanisms can be applied to preserve a deterministic order without sacrificing parallelism.

Constraints include the default dynamic scheduling strategy, the presence of shared static state, and the requirement to keep the test suite’s total runtime low.

1. Is @TestMethodOrder guaranteed to be respected when @Execution(ExecutionMode.CONCURRENT) is active?
2. What configuration options or annotations can enforce a specific execution order across threads?
3. Are there documented limits or recommended patterns for combining @TestMethodOrder with parallel execution?