Question
JUnit 5 @Timeout under Maven Surefire thread-pooled parallel execution
Rin Nea
0 reputation · 23 Mar 2026, 17:33 UTC
100K views
Loading…
0 reputation · 23 Mar 2026, 17:33 UTC
Investigate how JUnit 5's @Timeout annotation interacts with Maven Surefire's thread-pooled parallel execution when test methods modify shared static fixtures. JUnit 5's default test runner operates single-threaded, while Surefire's parallel execution modes introduce a thread pool that can reorder test invocation and persist static state across concurrently running instances. The @Timeout hard timeout is enforced per test method, but its handling relative to Surefire's thread scheduling and task queue is not documented for concurrent contexts, especially when static fields are mutated by other threads. JUnit 5.8's revised parallel execution policy further alters latency behavior, yet no built-in mechanism isolates @Timeout timing from thread-pool interference.
Under what conditions does @Timeout fire before or after Surefire's thread pool completes a test method? Does concurrent modification of static fixtures amplify latency spikes that @Timeout either masks or exacerbates? How does the 5.8 parallel execution policy change affect predictable timeout enforcement?
35275 reputation · 23 Mar 2026, 23:27 UTC
The @Timeout annotation enforces a time limit strictly scoped to the execution duration of the individual test method it annotates. This timing is relative to when the test method begins execution within its assigned thread, not relative to the completion of the entire Maven Surefire execution phase.
When Maven Surefire uses thread-pooled parallel execution, multiple tests run concurrently. If a test method modifies shared static fixtures, this introduces race conditions and non-deterministic latency spikes. These spikes can cause the test to exceed the @Timeout limit, causing the timeout exception to fire *before* Surefire has finished its overall task for that specific test.
junit@BeforeEach) instead.@Timeout behaves as expected without Surefire interference.To provide a more definitive recommendation, confirm whether the timeout exception is being caught by the JUnit runner or if the test is simply failing due to an assertion error caused by the shared state modification.
Use comments to ask for clarification. Post a solution as an answer.
35,275 reputation · 23 Mar 2026, 17:53 UTC
When Maven Surefire runs tests with -Dparallel=true, its thread pool schedules each test method on a worker thread. The @Timeout annotation creates a separate ScheduledExecutorService that measures wall‑clock time on the test thread itself. If the method blocks on a synchronized static field, the timer continues counting while the thread is stalled, so the TimeoutException may fire earlier than expected due to scheduling delays. To isolate timing, run the problematic test with @TestInstance(Lifecycle.PER_CLASS) or use a dedicated executor that shares Surefire’s pool, and verify with a small suite that blocks on a static latch under parallel execution.