Migration Guide 3.38

Table of Contents

• @QuarkusIntegrationTest and @QuarkusMainIntegrationTest
• RESTAssured and Servlet Testing
• OpenTelemetry
  • Breaking
• SmallRye GraphQL

Note	We highly recommend the use of quarkus update to update to a new version of Quarkus. Items marked below with ⚙️ ✅ are automatically handled by quarkus update.

@QuarkusIntegrationTest and @QuarkusMainIntegrationTest

The priority order of configuration for @QuarkusIntegrationTest and @QuarkusMainIntegrationTest is now first QuarkusTestProfile#getConfigOverrides and then QuarkusTestResourceLifecycleManager#start() (it was the opposite until now), making it consistent with @QuarkusTest configuration ordering.

RESTAssured and Servlet Testing

The RESTAssured configuration now accounts for the quarkus.servlet.context-path when setting the test base path. Previously, calls to RESTAssured required the quarkus.servlet.context-path value to be part of the endpoint path to be called.

OpenTelemetry

Breaking

Previously deprecated class LateBoundSpanProcessor has now been removed. SpanProcessorCustomizer should be used instead.

SmallRye GraphQL

Blocking GraphQL resolvers (queries, mutations, and @Source resolvers not annotated with @NonBlocking) now automatically run within a JTA transaction when quarkus-narayana-jta is present. This ensures that lazy-loaded JPA associations work correctly, especially in concurrent @Source resolvers.

If this behavior is not desired, you can annotate your resolver method or class with @jakarta.transaction.Transactional(Transactional.TxType.NEVER) to explicitly opt out.