Testing no exception thrown in JUnit - Build an Automation Script

Verify method completes without throwing any exception

Preconditions (2)

Step 1: Call the method 'processData' with input 'validInput'

Step 2: Observe if any exception is thrown during the method call

✅ Expected Result: The method 'processData' completes execution without throwing any exception

Automation Requirements - JUnit 5

Assertions Needed:

Verify that no exception is thrown when calling 'processData' with 'validInput'

Best Practices:

Use assertDoesNotThrow to check no exception is thrown

Keep test method names descriptive

Isolate the test to only check exception behavior

Automated Solution

JUnit

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

public class DataProcessorTest {

    @Test
    void processData_shouldNotThrowException_whenValidInput() {
        DataProcessor processor = new DataProcessor();
        assertDoesNotThrow(() -> processor.processData("validInput"));
    }
}

class DataProcessor {
    public void processData(String input) {
        // Simulate processing
        if (input == null) {
            throw new IllegalArgumentException("Input cannot be null");
        }
        // Processing logic here
    }
}

The test class DataProcessorTest uses JUnit 5.

The test method processData_shouldNotThrowException_whenValidInput clearly states what it tests.

Inside the test, we create an instance of DataProcessor and call processData with a valid string.

We use assertDoesNotThrow to verify that no exception is thrown during the call.

This method is the best practice to check that a method runs without exceptions in JUnit 5.

The DataProcessor class is included for completeness, showing a simple method that throws an exception only if input is null.

Common Mistakes - 3 Pitfalls

{'mistake': 'Using try-catch block inside test instead of assertDoesNotThrow', 'why_bad': 'It makes the test code longer and less readable, and may miss assertion failures if exceptions are swallowed.', 'correct_approach': "Use JUnit 5's assertDoesNotThrow to clearly express the intent and keep test concise."}

Not testing with valid input and assuming no exception

Using JUnit 4 style expected exception annotation for no exception scenario

Bonus Challenge

Now add data-driven testing with 3 different valid inputs to verify no exception is thrown for each

Show Hint