This issue intends to track move from JUnit 4 to JUnit Jupiter 5/6 across the WF codebase. We have put the work in on the ARQ side to make this possible, so we are ready to move. This Jira also provides simple summary of changes to make.

Summary of required and optional best practice changes:

• swap @RunWith(Arquillian.class) -> @ExtendWith(ArquillianExtension.class) (required)
• asserts now have different parameter order (required)
• methods no longer need to be public unless intended for override (best practice)
• JUnit 5 annotation inheritance doesn't work across packages or overrides - moved @OperateOnDeployment from method level to the parameter — JUnit 5 only looks at parameter annotations, not method-level ones (required)
• drop 'test' from method names e.g. testGracefulSimpleFailover → gracefulSimpleFailover (best practice)
• fix previously ignored spurious @Test on non-test helper methods (which would now fail) (required)
• swap arquillian-extension-byteman → byteman-bmunit5 (required)
• swap org.jboss.arquillian.extension.byteman.api.@BMRule/@BMRules imports → org.jboss.byteman.contrib.bmunit (what byteman-bmunit5 actually processes) (required)
• swap @WithByteman — the JUnit 5 equivalent of @RunWith(BMUnitRunner.class) (required)

The openrewrite recipes to use:

                    <activeRecipes>
                        <recipe>org.openrewrite.java.testing.junit5.JUnit4to5Migration</recipe>
                        <recipe>org.openrewrite.java.testing.junit5.JUnit5BestPractices</recipe>
                        <recipe>org.openrewrite.java.testing.arquillian.ArquillianJUnit4ToArquillianJUnit5</recipe>
                    </activeRecipes>

n.b. intentionally not using 'migrate' here as that's overloaded.