I’m working on converting a large project from Maven to Gradle. Part of it is an integration test suite where the tests must run in a certain order because they’re manipulating a real database, so test01 may create some resource, test02 modifies the resource, and test03 deletes the resource.
With Maven, we use JUnit and the @FixMethodOrder(MethodSorters.NAME_ASCENDING) annotation. With Gradle I’m using the same, but it doesn’t work consistently. Any tips or suggestions?
I tried making a minimal reproduction of the test ordering problem as a separate Gradle project, but in that context the tests are ordered properly. It’s only when I put the test in the context of our big project that the ordering seems to be ignored.