quarkusio/quarkus

Use parametrised tests for Hibernate ORM/Reactive interoperability

Open

#51,207 opened on Nov 24, 2025

View on GitHub
 (12 comments) (0 reactions) (0 assignees)Java (2,464 forks)batch import
area/hibernate-ormarea/hibernate-reactivegood first issuekind/enhancement

Repository metrics

Stars
 (12,967 stars)
PR merge metrics
 (Avg merge 6d 4h) (325 merged PRs in 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

Contributor guide

Research direction
Analyze the existing test suite for Hibernate interoperability and identify all combination scenarios. Then refactor the tests to use parameterized tests with explicit matrix of persistence unit types and configurations.
Tech stack
java
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaQuarkusHibernate ORM/Reactive
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65