assertThrows usage in JUnit - Build an Automation Script

Verify that a method throws the expected exception

Preconditions (2)

Step 1: Call the method with a negative input value

Step 2: Verify that the method throws IllegalArgumentException

✅ Expected Result: The test should pass only if IllegalArgumentException is thrown when the method is called with negative input

Automation Requirements - JUnit 5

Assertions Needed:

assertThrows to verify IllegalArgumentException is thrown

Best Practices:

Use lambda expression inside assertThrows

Check exception message if relevant

Keep test method names descriptive

Automated Solution

JUnit

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

class Calculator {
    int squareRoot(int number) {
        if (number < 0) {
            throw new IllegalArgumentException("Negative input not allowed");
        }
        return (int) Math.sqrt(number);
    }
}

public class CalculatorTest {

    @Test
    void testSquareRootThrowsExceptionForNegativeInput() {
        Calculator calculator = new Calculator();

        IllegalArgumentException exception = assertThrows(IllegalArgumentException.class, () -> {
            calculator.squareRoot(-5);
        });

        // Optional: verify exception message
        org.junit.jupiter.api.Assertions.assertEquals("Negative input not allowed", exception.getMessage());
    }
}

This test uses assertThrows from JUnit 5 to check that the squareRoot method throws an IllegalArgumentException when called with a negative number.

The lambda expression () -> calculator.squareRoot(-5) is passed to assertThrows. This means the code inside the lambda is executed and JUnit checks if the expected exception is thrown.

If the exception is thrown, the test passes. We also capture the exception object to verify its message matches the expected text. This helps ensure the exception is thrown for the right reason.

The test method name clearly describes what is being tested, which is a good practice.

Common Mistakes - 3 Pitfalls

Using try-catch block instead of assertThrows

Not using a lambda expression inside assertThrows

Not verifying the exception message

Bonus Challenge

Now add data-driven testing with 3 different negative inputs to verify the exception is thrown each time

Show Hint

Practice

1. What is the primary purpose of assertThrows in JUnit testing?

easy

A. To check if a specific exception is thrown by a code block

B. To verify the return value of a method

C. To measure the execution time of a method

D. To assert that no exceptions are thrown

Solution

1. Step 1: Understand the role of assertThrows

   assertThrows is used to test if a particular exception occurs when running a piece of code.

2. Step 2: Compare with other assertions

   Other assertions check values or states, but assertThrows specifically checks for exceptions.

3. Final Answer:

   To check if a specific exception is thrown by a code block -> Option A

4. Quick Check:

   assertThrows = Exception check [OK]

Hint: assertThrows checks exceptions thrown by code [OK]

Common Mistakes:

• Confusing assertThrows with assertEquals
• Using assertThrows to check return values
• Expecting assertThrows to measure performance

2. Which of the following is the correct syntax to use assertThrows in JUnit 5?

easy

A. assertThrows(Exception.class, () -> methodCall());

B. assertThrows(() -> methodCall(), Exception.class);

C. assertThrows(methodCall(), Exception.class);

D. assertThrows(Exception.class, methodCall());

Solution

1. Step 1: Recall assertThrows method signature

   The correct syntax is assertThrows(Exception.class, Executable) where Executable is a lambda or method reference.

2. Step 2: Analyze options

   assertThrows(Exception.class, () -> methodCall()); matches the correct syntax: exception class first, then lambda expression.

3. Final Answer:

   assertThrows(Exception.class, () -> methodCall()); -> Option A

4. Quick Check:

   assertThrows(Exception.class, lambda) = correct syntax [OK]

Hint: Exception class first, then lambda in assertThrows [OK]

Common Mistakes:

• Swapping parameters order
• Passing method call instead of lambda
• Omitting lambda expression

3. What will be the result of this JUnit 5 test code?

assertThrows(IllegalArgumentException.class, () -> {
  throw new IllegalArgumentException("Invalid argument");
});

medium

A. Test passes but ignores the exception message

B. Test fails because no exception is thrown

C. Test fails due to a syntax error

D. Test passes because the expected exception is thrown

Solution

1. Step 1: Check the exception thrown

   The lambda throws IllegalArgumentException, which matches the expected exception class.

2. Step 2: Understand assertThrows behavior

   assertThrows passes if the expected exception is thrown during execution.

3. Final Answer:

   Test passes because the expected exception is thrown -> Option D

4. Quick Check:

   Thrown exception matches expected = pass [OK]

Hint: assertThrows passes if expected exception is thrown [OK]

Common Mistakes:

• Thinking test fails if exception is thrown
• Confusing exception message with test result
• Assuming syntax error without checking code

4. Identify the error in this JUnit 5 test snippet:

assertThrows(NullPointerException.class, () -> {
  String s = null;
  s.length();
});

medium

A. Exception class should be RuntimeException.class

B. Lambda syntax is incorrect

C. No error; test will pass as NullPointerException is thrown

D. s.length() does not throw NullPointerException

Solution

1. Step 1: Analyze the code inside lambda

   Calling s.length() on a null string throws NullPointerException.

2. Step 2: Check assertThrows parameters

   Expected exception is NullPointerException.class, matching the thrown exception.

3. Final Answer:

   No error; test will pass as NullPointerException is thrown -> Option C

4. Quick Check:

   NullPointerException thrown and expected = pass [OK]

Hint: NullPointerException thrown matches expected exception [OK]

Common Mistakes:

• Assuming s.length() throws different exception
• Thinking lambda syntax is wrong
• Confusing exception class with superclass

5. Consider this test method:

void testDivideByZero() {
  ArithmeticException thrown = assertThrows(ArithmeticException.class, () -> {
    int result = 10 / 0;
  });
  assertEquals("/ by zero", thrown.getMessage());
}

What does this test verify beyond just exception throwing?

hard

A. It verifies the method returns zero

B. It verifies the exception message is exactly "/ by zero"

C. It verifies no exception is thrown

D. It verifies the exception type is RuntimeException

Solution

1. Step 1: Understand assertThrows return value

   assertThrows returns the thrown exception object, here stored in thrown.

2. Step 2: Analyze the assertEquals check

   The test checks that the exception message equals "/ by zero", verifying the exact error message.

3. Final Answer:

   It verifies the exception message is exactly "/ by zero" -> Option B

4. Quick Check:

   Exception message checked = It verifies the exception message is exactly "/ by zero" [OK]

Hint: assertThrows returns exception to check message [OK]

Common Mistakes:

• Thinking it checks return value of division
• Assuming exception type is RuntimeException
• Ignoring the message assertion