Hi Ant Developers, I'm working on the migration of Apache Cassandra project from JUnit 4 to JUnit 5 (CASSANDRA-16630 <https://issues.apache.org/jira/browse/CASSANDRA-16630>) which turned out to be larger than I originally expected. At the moment, three PRs got merged:
- https://github.com/apache/ant/pull/147 - https://github.com/apache/ant/pull/168 - https://github.com/apache/ant/pull/172 And there are a few more I'd like to discuss with you. Formatters Extensibility Apache Cassandra extended the existing JUnit 4 formatters in order to integrate them with a custom logic required for a better CI process. It was easily achievable for JUnit 4 since the formatters are marked public. On the contrary, for JUnit 5 all formatters are package private. Even *AbstractJUnitResultFormatter* is package private. Of course, we can copy-paste all these classes to our project and customize them based on our needs, but that seems to be a bit of an overhead. Currently, we'd like to make *AbstractJUnitResultFormatter *extensible. Here is the corresponding PR: https://github.com/apache/ant/pull/169/ I'd be happy to make other existing formatters extensible as well. Please, let me know if that sounds good to you and I'll add the changes to the existing PR or raise another one. Fork Mode Support Apache Cassandra is a large and complex product and in order to guarantee its quality we run many tests independently. It lets us ensure different test suites do not affect each other. For isolated testing we spin up a new JVM per tests suite via *forkMode* property. Unfortunately, *junitlauncher* task does not provide such a functionality. Currently, we'd like *mode* attribute to *fork* element. Here is the corresponding PR: https://github.com/apache/ant/pull/174 I'd be glad if you could provide some feedback on that. Also I need some guidance here - I have a suspicion that *JUnitLauncherTaskTest* is not being run during "./build clean test" (I cannot grep it in logs). Could you please help me to run this particular test from CLI. Use File Support Apache Cassandra does not always need to write testing output to a file. Even though it is possible to achieve writing into standard output (by overriding *TestResultFormatter.setDestination *method) instead of a file, it is impossible to prevent empty files from being created on the file system. Of course, we can delete these files, however, it would be nice to have the functionality similar to *junit* task. I've already started a related discussion on the PR (please, chime in): https://github.com/apache/ant/pull/171 I'd be very grateful to get code review comments on the PRs and your feedback on the above points. Best Regards, Aleksei Zotov.
