How to Continue Test Execution in JUnit 4 Even When an Assert Fails

How can I make my JUnit 4 tests continue executing after an assert fails?

// Sample test case in JUnit 4
import org.junit.*;
import static org.junit.Assert.*;

public class MyTest {
    @Test
    public void testMultipleAssertions() {
        try {
            assertEquals("Test 1 failed", 1, 2);
        } catch (AssertionError e) {
            System.out.println(e.getMessage());
        }
        try {
            assertEquals("Test 2 failed", 1, 1);
        } catch (AssertionError e) {
            System.out.println(e.getMessage());
        }
    }
}

When migrating from Jfunc (which supports non-blocking asserts) to JUnit 4, you may find that test execution stops upon the first assertion failure. JUnit 4 design promotes atomic tests, generally containing one assertion each, leading to clearer test failures. However, if you need to maintain the previous behavior of executing multiple asserts despite failures, you can achieve this with try-catch blocks around your assertions.

@Test
public void testWithContinuedExecution() {
    boolean assertion1Failed = false;
    boolean assertion2Failed = false;

    try {
        assertEquals("Check failed", 1, 2);
    } catch (AssertionError e) {
        assertion1Failed = true;
        System.out.println(e.getMessage());
    }

    try {
        assertEquals("Check succeeded", 1, 1);
    } catch (AssertionError e) {
        assertion2Failed = true;
        System.out.println(e.getMessage());
    }

    if (assertion1Failed || assertion2Failed) {
        fail("One or more assertions failed!");
    }
}  

Causes

• JUnit 4 is designed for atomic tests that halt on the first failure.
• Using multiple asserts within a single test method is discouraged in JUnit best practices.

Solutions

• Wrap each assertion in a try-catch block to handle failures without stopping subsequent assertions.
• Consider using the `AssertAll` pattern to aggregate assertion results for better reporting.

Mistake: Not using try-catch blocks to handle assertion errors.

Solution: Wrap assertions in try-catch to continue execution after failures.

Mistake: Failing to report all assertion results adequately.

Solution: Track failures and report them collectively at the end.