Why exception testing validates error handling in JUnit - Quick Recap

Recall & Review

beginner

What is exception testing in software testing?

Exception testing is a technique where tests are designed to check how software behaves when unexpected or error conditions occur, such as invalid inputs or system failures.

beginner

Why is exception testing important for error handling?

Exception testing ensures that the software correctly detects errors and responds properly, such as by throwing the right exceptions or showing meaningful messages, which helps prevent crashes and improves reliability.

intermediate

How does JUnit support exception testing?

JUnit allows you to write tests that expect exceptions using annotations like @Test(expected = Exception.class) or the assertThrows method, making it easy to verify that error handling works as intended.

beginner

What happens if exception testing fails?

If exception testing fails, it means the software did not handle the error as expected, which could lead to crashes, incorrect behavior, or security issues in real use.

intermediate

Give an example of exception testing in JUnit.

Example: Using assertThrows to check if a method throws IllegalArgumentException when given a bad input.

assertThrows(IllegalArgumentException.class, () -> { myMethod(null); });

What is the main goal of exception testing?

A To test user interface design

B To improve software speed

C To check if the software handles errors correctly

D To verify database connections

Exception testing focuses on verifying that the software properly handles error conditions.

Which JUnit feature helps test if a method throws an exception?

A @Test(expected = Exception.class)

B @BeforeEach

C @Ignore

D @AfterAll

The @Test annotation with expected parameter allows testing if a specific exception is thrown.

What does it mean if an exception test passes?

A The software crashed

B The software ran faster

C The software ignored the error

D The software correctly threw the expected exception

Passing exception tests means the software threw the expected exception, showing proper error handling.

Why should exception testing be part of QA?

A To reduce file size

B To ensure software reliability under error conditions

C To improve graphics quality

D To increase user clicks

Exception testing helps confirm that software behaves reliably when errors happen.

Which method in JUnit 5 is used to assert exceptions?

A assertThrows

B assertEquals

C assertTrue

D assertNull

assertThrows is used in JUnit 5 to check if a block of code throws a specific exception.

Explain why exception testing is essential for validating error handling in software.

Think about what happens when software faces unexpected problems.

Describe how you would write a JUnit test to check that a method throws an exception for invalid input.

Focus on JUnit syntax for exception testing.

Practice

1. Why is exception testing important in JUnit for validating error handling?

easy

A. It ensures the code correctly throws expected exceptions when errors occur.

B. It improves the speed of test execution by skipping error cases.

C. It automatically fixes bugs related to exceptions.

D. It prevents exceptions from being thrown during normal execution.

Solution

1. Step 1: Understand the purpose of exception testing

   Exception testing checks if the program throws the right error when something goes wrong.

2. Step 2: Connect exception testing to error handling validation

   By expecting specific exceptions, tests confirm the code handles errors as designed.

3. Final Answer:

   It ensures the code correctly throws expected exceptions when errors occur. -> Option A

4. Quick Check:

   Exception testing = Validates error handling [OK]

Hint: Exception tests confirm errors happen as expected [OK]

Common Mistakes:

• Thinking exception tests fix bugs automatically
• Believing exception tests speed up all tests
• Assuming exception tests stop exceptions from occurring

2. Which JUnit 5 syntax correctly tests that a method throws a NullPointerException?

easy

A. @Test
void test() {
assertThrows(NullPointerException, method());
}

B. @Test
void test() {
assertThrows(NullPointerException.class, () -> method());
}

C. @Test
void test() {
assertThrows(() -> method(), NullPointerException.class);
}

D. @Test
void test() {
assertThrows(method(), NullPointerException.class);
}

Solution

1. Step 1: Recall correct assertThrows syntax in JUnit 5

   The method is: assertThrows(ExceptionClass.class, Executable lambda).

2. Step 2: Match syntax to options

   @Test void test() { assertThrows(NullPointerException.class, () -> method()); } uses assertThrows with exception class first, then lambda, which is correct.

3. Final Answer:

   @Test void test() { assertThrows(NullPointerException.class, () -> method()); } -> Option B

4. Quick Check:

   assertThrows(Exception.class, () -> code) [OK]

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

Common Mistakes:

• Swapping argument order in assertThrows
• Passing method call instead of lambda
• Omitting .class for exception type

3. Given this JUnit 5 test code:

@Test
void testDivide() {
  assertThrows(ArithmeticException.class, () -> divide(10, 0));
}

int divide(int a, int b) {
  return a / b;
}

What will be the test result?

medium

A. Test fails due to syntax error in assertThrows usage.

B. Test fails because divide method returns 0 instead of throwing exception.

C. Test passes because dividing by zero throws ArithmeticException.

D. Test passes but throws NullPointerException instead.

Solution

1. Step 1: Analyze divide method behavior

   Dividing by zero in Java throws ArithmeticException automatically.

2. Step 2: Check assertThrows expectation

   The test expects ArithmeticException when dividing 10 by 0, matching actual behavior.

3. Final Answer:

   Test passes because dividing by zero throws ArithmeticException. -> Option C

4. Quick Check:

   Divide by zero throws ArithmeticException [OK]

Hint: Divide by zero throws ArithmeticException [OK]

Common Mistakes:

• Assuming divide returns 0 on zero divisor
• Confusing exception types
• Thinking assertThrows syntax is wrong here

4. Identify the error in this JUnit 5 test that tries to check for IllegalArgumentException:

@Test
void test() {
  assertThrows(IllegalArgumentException.class, method());
}

void method() {
  throw new IllegalArgumentException();
}

medium

A. assertThrows requires a string message as the first argument.

B. IllegalArgumentException is not a checked exception, so assertThrows is invalid.

C. The test method must declare throws IllegalArgumentException.

D. The method call should be inside a lambda, not called directly.

Solution

1. Step 1: Understand assertThrows parameter requirements

   assertThrows expects a lambda or Executable, not a direct method call.

2. Step 2: Identify the mistake in test code

   Calling method() directly runs it immediately, causing exception before assertThrows can catch it.

3. Final Answer:

   The method call should be inside a lambda, not called directly. -> Option D

4. Quick Check:

   Use lambda () -> method() in assertThrows [OK]

Hint: Wrap method call in lambda for assertThrows [OK]

Common Mistakes:

• Calling method directly inside assertThrows
• Thinking checked exceptions are required
• Adding unnecessary message argument

5. You want to test a method that throws IOException only when a file is missing. Which approach best validates this error handling using JUnit 5 exception testing?

hard

A. Use assertThrows(IOException.class, () -> method("missing.txt")) and verify exception message contains "not found".

B. Use assertThrows(Exception.class, () -> method("missing.txt")) without checking message.

C. Call method("missing.txt") directly and catch IOException in test method.

D. Use try-catch inside method to suppress IOException and assert no exception thrown.

Solution

1. Step 1: Choose specific exception type for assertThrows

   Testing for IOException ensures only that error triggers the test.

2. Step 2: Verify exception message for correctness

   Checking the message confirms the exception is due to missing file, not other IO errors.

3. Final Answer:

   Use assertThrows(IOException.class, () -> method("missing.txt")) and verify exception message contains "not found". -> Option A

4. Quick Check:

   Specific exception + message check = best validation [OK]

Hint: Test specific exception and check message for accuracy [OK]

Common Mistakes:

• Using generic Exception instead of IOException
• Not verifying exception message
• Suppressing exceptions inside method