Avoid cross-test config contamination in microprofile/telemetry tes…

…ts (helidon-io#9685) (helidon-io#9758) * Avoid cross-test config contamination Co-authored-by: Tim Quinn <[email protected]>
barchetta · Feb 7, 2025 · 6dad629 · 6dad629
1 parent e6f5ba3
commit 6dad629
Showing 1 changed file with 19 additions and 0 deletions.
diff --git a/microprofile/telemetry/pom.xml b/microprofile/telemetry/pom.xml
@@ -147,7 +147,26 @@
                         <configuration>
                             <systemPropertyVariables>
                                 <otel.bsp.schedule.delay>${otel.bsp.schedule.delay}</otel.bsp.schedule.delay>
+                                <otel.sdk.disabled>false</otel.sdk.disabled>
                             </systemPropertyVariables>
+                            <excludes>
+                                <exclude>**/AgentDetectorTest.java</exclude>
+                            </excludes>
+                        </configuration>
+                    </execution>
+                    <execution>
+                        <!--
+                        This test does not need an active OTel SDK so run it separately to prevent it from running first
+                        and leaving other tests with a no-op Otel which will cause them to fail.
+                         -->
+                        <id>agent-detector-tests</id>
+                        <goals>
+                            <goal>test</goal>
+                        </goals>
+                        <configuration>
+                            <includes>
+                                <include>**/AgentDetectorTest.java</include>
+                            </includes>
                         </configuration>
                     </execution>
                 </executions>