WildFly 33 Final BOM depends on Arquillian 1.8.1.Final that is not working with JUnit 5 (tracked by https://github.com/arquillian/arquillian-core/issues/576).

Any user using our BOMs to test their applications against WildFly with Arquillian + JUnit 5 will see new failures.

To work around this regression, they must explicitly bump the Arquillian version in their pom.xml

        <dependency>
            <groupId>org.jboss.arquillian.junit5</groupId>
            <artifactId>arquillian-junit5-container</artifactId>
            <!-- temporary overriding as the 1.9.0.Final version pulled by
                 WildFly BOM does not work with JUnit 5
            -->
            <version>1.9.0.Final</version>
            <scope>test</scope>
        </dependency>

The fix for this will be to upgrade Arquillian Core to 1.9.1.Final, Arquillian Jakarta to 10.0.0.Final and WildFly Arquillian to 5.1.0.Beta4.

Arquillian Core:

Tag: https://github.com/arquillian/arquillian-core/releases/tag/1.9.1.Final
Diff: https://github.com/arquillian/arquillian-core/compare/1.8.1.Final...1.9.1.Final

Arquillian Jakarta

Note the only change here is the version number.

Tag: https://github.com/arquillian/arquillian-jakarta/releases/tag/10.0.0.Final
Diff: https://github.com/arquillian/arquillian-jakarta/compare/1.8.1.Final...10.0.0.Final

WildFly Arquillian

Tag: https://github.com/wildfly/wildfly-arquillian/releases/tag/5.1.0.Beta4
Diff: https://github.com/wildfly/wildfly-arquillian/compare/5.1.0.Beta3...5.1.0.Beta4