Support Assumptions.assumeThat in Quarkus

[liamzwbao]

Description

Currently, AssertJ's Assumptions (e.g., org.assertj.core.api.Assumptions.assumeThat) do not work as expected within Quarkus tests. Unlike JUnit’s Assumptions.assumeTrue, which properly skips tests when the assumption fails, AssertJ’s assumption throws an exception instead of skipping the test.

Expected Behavior

• When using org.assertj.core.api.Assumptions.assumeThat(condition).isTrue(), the test should be skipped rather than failing with an exception.

Actual Behavior

• The test fails with an exception instead of being skipped.

Example

import io.quarkus.test.junit.QuarkusTest;
import org.junit.jupiter.api.Assumptions;
import org.junit.jupiter.api.Test;

@QuarkusTest
class QuarkusAssertJTest {

  private boolean supportFeature() {
    return false;
  }

  @Test
  void testQuarkusJunitAssumptions() {
    // Will skip
    Assumptions.assumeTrue(supportFeature());
  }

  @Test
  void testQuarkusAssertJAssumptions() {
    // Will throw exception
    org.assertj.core.api.Assumptions.assumeThat(supportFeature()).isTrue();
  }
}

[geoand]

Does this work properly in a non-Quarkus JUnit5 test?

[liamzwbao]

Does this work properly in a non-Quarkus JUnit5 test?

Yes, the two tests are skipped if I remove the @QuarkusTest annotation.

[geoand]

Thanks

[geoand]

I tried this and both JUnit5 and AssertJ assumptions worked as expected

[liamzwbao]

I tried this and both JUnit5 and AssertJ assumptions worked as expected

Hi @geoand, I tested it again and found that the root cause is AssertJ using org.junit.AssumptionViolatedException for Junit4 instead of org.opentest4j.TestAbortedException for Junit5. To resolve this, I had to explicitly set:

org.assertj.core.api.Assumptions.setPreferredAssumptionException(
        PreferredAssumptionException.JUNIT5);

to make it work. This seems like a config issue. Do you have any insights why Junit4 exception is not suppressed when I add @QuarkusTest annotation? Thanks!

[geoand]

Interesting.

I don't have any additional insights unfortunately. Figuring out what's going on would require debugging AssertJ