Cucumber JVM 7.x step definition compatibility with JUnit 5 test runner

Evaluating the interoperability boundary between Cucumber JVM version upgrades and the associated testing framework runtime remains ambiguous when step definitions fail to load.

Glue-code compatibility between Cucumber JVM 6.x and 7.x frequently introduces silent failures and version mismatches with JUnit or TestNG can exacerbate detection gaps. The --dry-run flag validates step definitions but may not surface framework-level incompatibilities. Similarly cucumber.yml profile reversion offers a configuration rollback point yet its effectiveness across major version jumps is unverified.

Under what conditions does --dry-run confirm cross-version step definition validity? Does cucumber.yml profile reversion reliably restore functionality after a JVM major upgrade? How do JUnit 5 versus TestNG runtime differences influence the detection of glue-code breakage?