Charlee Chitsuk

Do we have any update on this issue?

Hi @ingwarsw, I've followed this repository example at https://github.com/ingwarsw/arquillian-suite-extension/tree/master/test-suites/junit5 and implemented as https://github.com/charleech/arquillian-junit5-payara/tree/main/my-cdi-junit5-multiple-tester as the following example: - ```java @ArquillianSuiteDeployment public class ArquillianSuiteDeployments { @Deployment(name = "payara-evaluation-base") public static WebArchive...

Anyhow when I've tried to use the workaround test suite as mentioned at the formal `JUnit5` document as the following: - * https://junit.org/junit5/docs/current/user-guide/#running-tests-junit-platform-runner * https://junit.org/junit5/docs/current/user-guide/#running-tests-junit-platform-runner-test-suite * https://stackoverflow.com/questions/50565724/are-test-suites-considered-deprecated-in-junit5 I also have...

I'm not sure if it is possible to enhance the `arquillian-suite-extension` so that it may support the `JUnit5` _test suite_ or not. Could you please help to consider and advise?

I've just found that the **JUnit 5** version `5.8.0-M1` and `org.junit.platform:junit-platform-suite:1.0.8-M1` introduces `@Suite` natively (_without any dependency to JUnit 4 anymore_) as the following :- * https://junit.org/junit5/docs/snapshot/user-guide/#junit-platform-suite-engine * https://github.com/junit-team/junit5/pull/2416 Then...

It would be great if this will support for the _Multi-root Workspaces_ and _Multiple Projects_ in same parent directory.

Surprisingly, it works fine with JDK 11 ! #### JDK openjdk version "11.0.20" 2023-07-18 OpenJDK Runtime Environment Temurin-11.0.20+8 (build 11.0.20+8) OpenJDK 64-Bit Server VM Temurin-11.0.20+8 (build 11.0.20+8, mixed mode) ####...

After searching through the internet with trial and error, I'm able to make it works with `JDK 17` by adding the JVM argument as the following: - ```bash export JAVA_TOOL_OPTIONS="-Djdk.util.zip.disableZip64ExtraFieldValidation=true...

Even the test is success, the stopping process is too slow. It takes around *__2+ minutes__*. I also have a chance to dig deeper and found that the slowness is...

I have a chance to add the failure test case as the following: - ```java @Test @Order(2) @DisplayName( "When greeting as failure by Jakarta EE should be failed." ) void...