Why fast tests enable frequent runs in JUnit - Automation Benefits in Action

Verify that a fast unit test runs quickly and passes

Preconditions (2)

Step 1: Create a test method that calls a simple function returning a fixed value

Step 2: Run the test method

Step 3: Measure the test execution time

Step 4: Verify the test passes quickly (under 100 milliseconds)

✅ Expected Result: The test passes successfully and completes quickly, demonstrating that fast tests enable frequent runs.

Automation Requirements - JUnit 5

Assertions Needed:

Assert that the method returns the expected value

Assert that the test execution time is less than 100 milliseconds

Best Practices:

Use @Test annotation for test methods

Use Assertions.assertEquals for value verification

Use System.nanoTime() to measure execution time

Keep tests isolated and fast

Avoid Thread.sleep or unnecessary waits

Automated Solution

JUnit

import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;

public class FastTestExample {

    // Simple method to test
    public int getFixedValue() {
        return 42;
    }

    @Test
    public void testGetFixedValueIsFast() {
        long startTime = System.nanoTime();
        int result = getFixedValue();
        long endTime = System.nanoTime();
        long durationMillis = (endTime - startTime) / 1_000_000;

        assertEquals(42, result, "The method should return 42");
        assertTrue(durationMillis < 100, "Test should run under 100 milliseconds but took " + durationMillis + " ms");
    }
}

This test class FastTestExample contains a simple method getFixedValue() that returns 42.

The test method testGetFixedValueIsFast() measures the time before and after calling the method using System.nanoTime(). It calculates the duration in milliseconds.

It asserts two things: the method returns the expected value 42, and the test runs quickly (under 100 milliseconds). This shows how fast tests can run frequently without slowing down development.

Using JUnit 5 annotations and assertions keeps the test clear and maintainable.

Common Mistakes - 3 Pitfalls

Using Thread.sleep() to simulate delays in tests

Not measuring test execution time

Testing complex logic in one test

Bonus Challenge

Now add data-driven testing with 3 different input values to verify the method returns expected results quickly.

Show Hint