Failure notification setup in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the JUnit Test annotation.

JUnit

import org.junit.[1];

public class SampleTest {
    @Test
    public void testExample() {
        // test code
    }
}

Drag options to blanks, or click blank then click option'

AAfter

BBefore

CTest

DIgnore

Attempts:

3 left

💡 Hint

Common Mistakes

Using @Before or @After instead of @Test

Forgetting to import the annotation

The @Test annotation marks a method as a test method in JUnit.

2fill in blank

medium

Complete the code to assert that two values are equal.

JUnit

import static org.junit.Assert.[1];

public class SampleTest {
    @Test
    public void testSum() {
        int result = 2 + 3;
        assertEquals(5, result);
    }
}

Drag options to blanks, or click blank then click option'

AassertTrue

BassertEquals

CassertNull

DassertNotNull

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertTrue with equality instead of assertEquals

Not importing the assertion method

assertEquals checks if two values are equal in JUnit tests.

3fill in blank

hard

Fix the error in the test method to notify failure correctly.

JUnit

import static org.junit.Assert.assertEquals;

public class SampleTest {
    @Test
    public void testFailNotification() {
        int expected = 10;
        int actual = 5;
        assertEquals([1], actual);
    }
}

Drag options to blanks, or click blank then click option'

Aexpected

Bactual

C15

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping expected and actual values

Using a wrong literal value

The first argument to assertEquals is the expected value, then the actual value.

4fill in blank

hard

Fill both blanks to create a test that fails with a custom message.

JUnit

import static org.junit.Assert.assertEquals;

public class SampleTest {
    @Test
    public void testFailWithMessage() {
        assertEquals([1], [2], 100);
    }
}

Drag options to blanks, or click blank then click option'

A"Failure: values differ"

B100

C50

D"Test passed"

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the message in the wrong position

Using the actual value instead of expected

The first argument is the failure message, the second is the expected value.

5fill in blank

hard

Fill all three blanks to write a test that fails if a condition is false with a message.

JUnit

import static org.junit.Assert.assertTrue;

public class SampleTest {
    @Test
    public void testCondition() {
        assertTrue([1], [2] > [3]);
    }
}

Drag options to blanks, or click blank then click option'

A"Check if x is greater than y"

Bx

Cy

D"Condition met"

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping x and y in the condition

Using the wrong message or no message

The first argument is the failure message, then the condition checks if x is greater than y.

Practice

1. What is the primary purpose of setting up failure notification in JUnit tests?

easy

A. To get alerts immediately when a test fails

B. To speed up test execution

C. To automatically fix failed tests

D. To skip tests that might fail

Solution

1. Step 1: Understand failure notification purpose

   Failure notification is designed to alert developers right when a test fails so they can act quickly.

2. Step 2: Eliminate unrelated options

   Speeding tests, auto-fixing, or skipping tests are not related to failure notifications.

3. Final Answer:

   To get alerts immediately when a test fails -> Option A

4. Quick Check:

   Failure notification = Immediate alerts [OK]

Hint: Failure notification means alerts on test failure [OK]

Common Mistakes:

• Thinking it speeds up tests
• Assuming it fixes tests automatically
• Believing it skips tests

2. Which JUnit feature is commonly used to detect test failures and trigger notifications?

easy

A. TestRule

B. TestSuite

C. TestWatcher

D. TestRunner

Solution

1. Step 1: Identify JUnit classes for failure detection

   TestWatcher is a JUnit rule designed to watch test execution and detect failures.

2. Step 2: Compare with other options

   TestRule is a general interface, TestSuite groups tests, TestRunner runs tests but does not notify failures.

3. Final Answer:

   TestWatcher -> Option C

4. Quick Check:

   Failure detection = TestWatcher [OK]

Hint: TestWatcher watches tests and detects failures [OK]

Common Mistakes:

• Confusing TestRule interface with TestWatcher
• Thinking TestSuite handles failure notifications
• Assuming TestRunner sends alerts

3. Given the following JUnit snippet, what will happen when the test fails?

public class MyTest {
  @Rule
  public TestWatcher watcher = new TestWatcher() {
    @Override
    protected void failed(Throwable e, Description d) {
      System.out.println("Test failed: " + d.getMethodName());
    }
  };

  @Test
  public void testFail() {
    assertEquals(1, 2);
  }
}

medium

A. Sends an email automatically

B. Test passes silently without output

C. Throws a runtime exception and stops tests

D. Prints 'Test failed: testFail' to the console

Solution

1. Step 1: Understand TestWatcher failed() method

   The failed() method runs when a test fails and prints the method name.

2. Step 2: Analyze the testFail() method

   assertEquals(1, 2) fails, triggering failed() to print the message.

3. Final Answer:

   Prints 'Test failed: testFail' to the console -> Option D

4. Quick Check:

   Failed test triggers failed() print [OK]

Hint: Failed test triggers failed() print message [OK]

Common Mistakes:

• Thinking test passes silently
• Expecting automatic email without code
• Assuming runtime exception stops all tests

4. Identify the error in this JUnit failure notification setup:

public class NotifyTest {
  @Rule
  public TestWatcher watcher = new TestWatcher() {
    @Override
    protected void failed() {
      System.out.println("Failure detected");
    }
  };

  @Test
  public void testExample() {
    fail();
  }
}

medium

A. Missing parameters in failed() method override

B. @Rule annotation is misplaced

C. fail() method is undefined

D. TestWatcher cannot be used with @Rule

Solution

1. Step 1: Check failed() method signature

   TestWatcher.failed() requires parameters (Throwable, Description) to override correctly.

2. Step 2: Verify other parts

   @Rule is correctly placed, fail() is a JUnit method, TestWatcher works with @Rule.

3. Final Answer:

   Missing parameters in failed() method override -> Option A

4. Quick Check:

   Override failed() with correct parameters [OK]

Hint: Override failed(Throwable, Description) exactly [OK]

Common Mistakes:

• Omitting parameters in failed() override
• Misplacing @Rule annotation
• Confusing fail() method usage

5. You want to send an email alert whenever a JUnit test fails. Which approach correctly integrates this using TestWatcher?

public class EmailAlertTest {
  @Rule
  public TestWatcher watcher = new TestWatcher() {
    @Override
    protected void failed(Throwable e, Description d) {
      // What should go here?
    }
  };

  @Test
  public void testEmail() {
    assertTrue(false);
  }
}

hard

A. Use @After annotation to send email after all tests

B. Call a method to send email inside failed(), passing e and d

C. Throw a new exception inside failed() to trigger email

D. Print stack trace only; email sending is automatic

Solution

1. Step 1: Understand TestWatcher failed() role

   failed() runs on test failure; it is the right place to trigger email sending.

2. Step 2: Choose correct action inside failed()

   Calling a method to send email with failure details is correct; throwing exceptions or relying on @After is incorrect.

3. Final Answer:

   Call a method to send email inside failed(), passing e and d -> Option B

4. Quick Check:

   Send email in failed() method [OK]

Hint: Send email inside failed() override [OK]

Common Mistakes:

• Throwing exceptions to send email
• Using @After for failure alerts
• Assuming email sends automatically without code