afs opened a new issue, #3236: URL: https://github.com/apache/jena/issues/3236
jena-core testing is mixture of JUnit3 and JUnit4. This risks missing tests from surefire. (Some JUnit4-only tests were being missed because discovery wasn't finding them.) There does not appear to be any blockers for moving updating everything to JUnit4 (transition), then to JUnit5 now contract testing is no longer used. JUnit4 to JUnit5 is a simpler task. Going via JUnit4 reduced the chances of missing things. The test would still be organised into test suites, not relying on discovery to check that everything is being run. Elsewhere, Jena has some custom JUnit4 test runners that build tests from manifestsfor RDF, SPARQL, SHACL and ShEx. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
