Increase test fault tolerance by removing SpanFactory usage

Increase test fault tolerance by removing SpanFactory usage #2021
AxonFramework · Sep 6, 2022 · b94ca3d · b94ca3d
1 parent 2e309b0
commit b94ca3d
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/...est/java/org/axonframework/integrationtests/eventhandling/TrackingEventProcessorTest.java b/...est/java/org/axonframework/integrationtests/eventhandling/TrackingEventProcessorTest.java
@@ -49,6 +49,7 @@
 import org.axonframework.messaging.StreamableMessageSource;
 import org.axonframework.messaging.unitofwork.CurrentUnitOfWork;
 import org.axonframework.serialization.SerializationException;
+import org.axonframework.tracing.NoOpSpanFactory;
 import org.axonframework.tracing.TestSpanFactory;
 import org.hamcrest.CoreMatchers;
 import org.junit.jupiter.api.*;
@@ -1963,6 +1964,11 @@ void refuseStartDuringShutdown() throws Exception {
     @Test
     @Timeout(value = 1000)
     void isReplayingWhenNotCaughtUp() throws Exception {
+        initProcessor(
+                TrackingEventProcessorConfiguration.forSingleThreadedProcessing()
+                                                   .andEventAvailabilityTimeout(100, TimeUnit.MILLISECONDS),
+                builder -> builder.spanFactory(NoOpSpanFactory.INSTANCE)
+        );
         when(mockHandler.supportsReset()).thenReturn(true);
 
         final List<String> handled = new CopyOnWriteArrayList<>();