Use parametrised tests for Hibernate ORM/Reactive interoperability
#51.207 aberto em 24 de nov. de 2025
Métricas do repositório
- Stars
- (12.967 stars)
- Métricas de merge de PR
- (Mesclagem média 6d 4h) (325 fundiu PRs em 30d)
Description
Description
The discussion in https://github.com/quarkusio/quarkus/pull/51159 highlighted that users combine Hibernate ORM and Hibernate Reactive in different ways. For example, users may:
- Use both blocking and reactive access within the same persistence unit
- Use separate persistence units for blocking and reactive
- Rely on default persistence units only, or mixed with named
- Encounter negative scenarios, such as misspelled datasource or PU names
The current compatibility test suite (io.quarkus.hibernate.reactive.compatibility) encodes these scenarios in a denormalized way, which makes it difficult to understand the complete coverage and has confusing test names such as ORMReactiveCompatbilityDifferentNamedDataSourceNamedPersistenceUnitBothUnitTest.
As a result, certain edge cases may already be untested.
Refactoring the suite to use parameterized tests would make the matrix of supported combinations explicit and easier to reason about.
To be done after https://github.com/quarkusio/quarkus/issues/51206
Implementation ideas
No response