MethodOrderer that allows to explicitly specify that the default ordering should be applied.

If the junit.jupiter.testmethod.order.default is set, specifying this MethodOrderer has the same effect as referencing the configured class directly. Otherwise, it has the same effect as not specifying any MethodOrderer.

This class can be used to reset the MethodOrderer for a @Nested class and its @Nested inner classes, recursively, when a MethodOrderer is configured using @TestMethodOrder on an enclosing class.

public void orderMethods(MethodOrdererContext context) {
    Collections.shuffle(context.getMethodDescriptors());
}

MethodOrderer that sorts methods alphanumerically based on their display names using String#compareTo(String)

MethodOrderer that sorts methods alphanumerically based on their names using String#compareTo(String).

If two methods have the same name, String representations of their formal parameter lists will be used as a fallback for comparing the methods.

MethodOrderer that sorts methods based on the @Order annotation.

Any methods that are assigned the same order value will be sorted arbitrarily adjacent to each other.

Any methods not annotated with @Order will be assigned the default order value which will effectively cause them to appear at the end of the sorted list, unless certain methods are assigned an explicit order value greater than the default order value. Any methods assigned an explicit order value greater than the default order value will appear after non-annotated methods in the sorted list.

MethodOrderer that orders methods pseudo-randomly.

Custom Seed

By default, the random seed used for ordering methods is the value returned by System#nanoTime() during static class initialization. In order to support repeatable builds, the value of the default random seed is logged at CONFIG level. In addition, a custom seed (potentially the default seed from the previous test plan execution) may be specified via the junit.jupiter.execution.order.random.seed configuration parameter which can be supplied via the Launcher API, build tools (e.g., Gradle and Maven), a JVM system property, or the JUnit Platform configuration file (i.e., a file named junit-platform.properties in the root of the class path). Consult the User Guide for further information.