I see that Junit5 completely breaks parameterization because its test running is completely different...the value gets passed as a parameter to the test method, which is too late for any test setup. As a result, all s3a ITests are broken.
The good news, JUnit 5.13 appears to restore this functionality, somehow https://docs.junit.org/current/api/org.junit.jupiter.params/org/junit/jupiter/params/ParameterizedClass.html I'm trying this on a new test suite I'm writing; if it works we will have to move all those parameterized test cases in hadoop-aws, maybe elsewhere back to it. I'm a bit disappointed with the Junit team here, though their key contribution to software development "make writing tests easy" is profound. Pity they left out "make upgrading existing test suites easy"
