assertThrows for exceptions in JUnit - Framework Patterns

Framework Mode - assertThrows for exceptions

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTests.java
                ├── utils/
                │   └── TestUtils.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Test Classes: Contain test methods using assertThrows to verify exceptions.
• Page Objects: Encapsulate UI elements and actions (e.g., LoginPage).
• Utilities: Helper methods for common tasks like data setup or exception message validation.
• Configuration: Manage environment settings, credentials, and test parameters.
• Driver Layer: Manages WebDriver setup and teardown for browser automation.

Configuration Patterns

• Environment Properties: Use TestConfig.java or application.properties to define URLs, credentials, and environment-specific settings.
• Browser Setup: Configure browser type and options in setup methods or config files.
• Exception Handling: Centralize expected exception types and messages for reuse in tests.
• JUnit Annotations: Use @BeforeEach and @AfterEach for setup and cleanup.

Test Reporting and CI/CD Integration

• Use JUnit's built-in reporting for test pass/fail results including exception assertions.
• Integrate with CI tools like Jenkins or GitHub Actions to run tests automatically on code changes.
• Generate HTML or XML reports using plugins like Surefire or Allure for detailed test results.
• Fail tests clearly when assertThrows does not catch the expected exception.

Best Practices

1. Use assertThrows to clearly specify the expected exception type and test only the code that should throw it.
2. Keep exception messages simple and consistent to make assertions reliable.
3. Write one assertion per test method to keep tests focused and easy to understand.
4. Use descriptive test method names that explain what exception is expected and why.
5. Centralize exception-related constants or helper methods in utility classes for reuse.

Self Check

Where in this folder structure would you add a new test method that verifies a NullPointerException is thrown when a required input is missing?

Key Result

Use assertThrows in test classes to verify expected exceptions clearly and reliably.

Practice

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

easy

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

B. To verify the return value of a method

C. To measure the execution time of a method

D. To skip a test case conditionally

Solution

1. Step 1: Understand the role of assertThrows

   assertThrows is designed to check if a certain exception occurs when running some code.

2. Step 2: Compare with other options

   Options B, C, and D describe different test functions unrelated to exception checking.

3. Final Answer:

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

4. Quick Check:

   assertThrows checks exceptions = A [OK]

Hint: Remember: assertThrows tests exceptions thrown by code [OK]

Common Mistakes:

• Confusing assertThrows with assertEquals
• Thinking assertThrows measures performance
• Using assertThrows to skip tests

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 the method signature

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

2. Step 2: Check each option

   assertThrows(Exception.class, () -> methodCall()); matches the correct order and lambda usage. Options A, B, and D have wrong argument order or missing lambda.

3. Final Answer:

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

4. Quick Check:

   Exception class first, then lambda = C [OK]

Hint: Exception class first, then lambda with code [OK]

Common Mistakes:

• Swapping the order of arguments
• Passing method call instead of lambda
• Omitting the lambda expression

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

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

@Test
void testDivideByZero() {
  assertThrows(ArithmeticException.class, () -> {
    int result = 10 / 0;
  });
}

medium

A. Test passes but exception type is wrong

B. Test fails because no exception is thrown

C. Test fails due to syntax error

D. Test passes because ArithmeticException is thrown

Solution

1. Step 1: Analyze the code inside assertThrows

   The code divides 10 by 0, which throws an ArithmeticException at runtime.

2. Step 2: Check if exception matches expected

   assertThrows expects ArithmeticException.class, which matches the thrown exception.

3. Final Answer:

   Test passes because ArithmeticException is thrown -> Option D

4. Quick Check:

   Exception thrown matches expected = A [OK]

Hint: Divide by zero throws ArithmeticException [OK]

Common Mistakes:

• Assuming no exception is thrown
• Confusing exception types
• Thinking test fails on exception

4. Identify the error in this JUnit test using assertThrows:

@Test
void testNullPointer() {
  assertThrows(NullPointerException, () -> {
    String s = null;
    s.length();
  });
}

medium

A. Lambda syntax is incorrect

B. NullPointerException is not thrown here

C. Missing .class after NullPointerException

D. assertThrows cannot test NullPointerException

Solution

1. Step 1: Check the exception argument

   The exception class must be passed as NullPointerException.class, not just the class name.

2. Step 2: Verify lambda and exception thrown

   The lambda syntax is correct and the code throws NullPointerException as expected.

3. Final Answer:

   Missing .class after NullPointerException -> Option C

4. Quick Check:

   Exception class needs .class suffix = B [OK]

Hint: Always add .class after exception name in assertThrows [OK]

Common Mistakes:

• Omitting .class after exception
• Miswriting lambda syntax
• Assuming exception not thrown

5. You want to test that a method parseNumber(String s) throws NumberFormatException only when the input is not a valid number. Which of these tests correctly uses assertThrows to check this behavior?

hard

A. assertThrows(NumberFormatException.class, () -> parseNumber(123));

B. assertThrows(NumberFormatException.class, () -> parseNumber("abc"));

C. assertThrows(Exception.class, () -> parseNumber(null));

D. assertThrows(NumberFormatException.class, () -> parseNumber("123"));

Solution

1. Step 1: Understand the method behavior

   parseNumber should throw NumberFormatException for invalid strings like "abc" but not for valid numbers like "123".

2. Step 2: Evaluate each test case

   assertThrows(NumberFormatException.class, () -> parseNumber("abc")); tests invalid input "abc" correctly. assertThrows(NumberFormatException.class, () -> parseNumber("123")); tests valid input, so no exception expected. assertThrows(Exception.class, () -> parseNumber(null)); uses a different exception and null input. assertThrows(NumberFormatException.class, () -> parseNumber(123)); passes an integer instead of string, causing compile error.

3. Final Answer:

   assertThrows(NumberFormatException.class, () -> parseNumber("abc")); -> Option B

4. Quick Check:

   Test invalid input throws NumberFormatException = D [OK]

Hint: Test invalid strings with assertThrows for NumberFormatException [OK]

Common Mistakes:

• Testing valid input expecting exception
• Passing wrong argument types
• Using wrong exception class