[wildfly-dev] Re: Migrating Testsuite Maven Modules to JUnit 5

As a general topic, this is something I've been looking at for a while. I've submitted the first migration [1] for the smoke tests. Please note that if you've got an open PR that touches the smoke tests, you will likely need to update it. For the future, I would like to slowly migrate Maven modules (subprojects) as well. This will not be a fast moving migration nor is there anything component leads need to specifically do with this migration. However, if you're interested in helping please reach out to me. We want to be very careful with what we change and when we change it. We really need to make sure we coordinate every change. Why should we do this? In general JUnit 5 is the path forward for JUnit testing. While JUnit 4 still works, there could be a point where it won't work on newer versions of Java. I suspect changes will not be made to JUnit 4o to fix that. In my opinion, this is a good step forward and JUnit 5 is a much more pleasant experience with modern Java. Some very small examples of what can be done can be seen in the, probably poorly named, WildFly Arquillian JUnit API [2[. [1]: https://github.com/wildfly/wildfly/pull/19032 [2]: https://github.com/wildfly/wildfly-arquillian/tree/main/junit-api James R. Perkins Principal Software Engineer Red Hat <https://www.redhat.com/> <https://www.redhat.com/> _______________________________________________ wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org Privacy Statement: https://www.redhat.com/en/about/privacy-policy List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...