@Order for execution order in JUnit - Build an Automation Script

Verify test methods execute in specified order using @Order annotation

Preconditions (2)

Step 1: Create a test class annotated with @TestMethodOrder(OrderAnnotation.class)

Step 2: Add three test methods annotated with @Test and @Order with values 1, 2, and 3 respectively

Step 3: Inside each test method, print or log a unique message indicating its execution

Step 4: Run the test class

Step 5: Observe the order of test execution in the test report or console output

✅ Expected Result: Test methods execute in the order defined by their @Order values: method with @Order(1) runs first, then @Order(2), then @Order(3)

Automation Requirements - JUnit 5

Assertions Needed:

Verify that test methods run in the order specified by their @Order annotation

Best Practices:

Use @TestMethodOrder(OrderAnnotation.class) at class level

Use @Order annotation on each test method with unique integer values

Avoid relying on default test execution order

Keep test methods independent and idempotent

Automated Solution

JUnit

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.Order;
import org.junit.jupiter.api.TestMethodOrder;
import org.junit.jupiter.api.MethodOrderer.OrderAnnotation;
import static org.junit.jupiter.api.Assertions.assertTrue;

@TestMethodOrder(OrderAnnotation.class)
public class OrderedTests {

    private static final StringBuilder executionOrder = new StringBuilder();

    @Test
    @Order(1)
    void firstTest() {
        executionOrder.append("1");
        assertTrue(true);
    }

    @Test
    @Order(2)
    void secondTest() {
        executionOrder.append("2");
        assertTrue(true);
    }

    @Test
    @Order(3)
    void thirdTest() {
        executionOrder.append("3");
        assertTrue(true);
        // Verify the order after all tests run
        String order = executionOrder.toString();
        assertTrue(order.equals("123"), "Tests did not run in order 1,2,3 but in order: " + order);
    }
}

This test class uses @TestMethodOrder(OrderAnnotation.class) to specify that test methods run in the order defined by their @Order annotations.

Each test method appends its order number to a shared StringBuilder. The last test method asserts that the combined execution order string is "123", confirming the tests ran in the correct sequence.

Assertions inside each test ensure the test runs and the final assertion verifies the execution order.

Common Mistakes - 4 Pitfalls

Not annotating the class with @TestMethodOrder(OrderAnnotation.class)

Using duplicate @Order values on multiple test methods

{'mistake': 'Relying on test execution order without explicit @Order annotations', 'why_bad': "JUnit's default order is not guaranteed and can change, causing flaky tests.", 'correct_approach': 'Use @Order annotations with @TestMethodOrder to explicitly control execution order.'}

Making tests dependent on execution order for correctness

Bonus Challenge

Now add data-driven testing with 3 different sets of inputs and verify the order of execution for each data set

Show Hint