Why JUnit is the standard for Java testing - Automation Benefits in Action

Verify JUnit test execution and assertion

Preconditions (2)

Step 1: Create a simple Java class Calculator with a method add(int a, int b) that returns the sum

Step 2: Create a JUnit test class CalculatorTest

Step 3: Write a test method testAdd that calls add(2, 3)

Step 4: Use an assertion to verify the result is 5

Step 5: Run the test using JUnit

Step 6: Observe the test result

✅ Expected Result: The test passes successfully, confirming that JUnit runs the test and validates the assertion

Automation Requirements - JUnit 5

Assertions Needed:

Assert that the sum returned by add(2, 3) equals 5

Best Practices:

Use @Test annotation for test methods

Use assertEquals for checking expected vs actual values

Keep test methods small and focused

Use descriptive method names

Run tests automatically with JUnit runner

Automated Solution

JUnit

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

public class Calculator {
    public int add(int a, int b) {
        return a + b;
    }
}

public class CalculatorTest {
    @Test
    void testAdd() {
        Calculator calc = new Calculator();
        int result = calc.add(2, 3);
        assertEquals(5, result, "2 + 3 should equal 5");
    }
}

This code defines a simple Calculator class with an add method. The CalculatorTest class uses JUnit 5's @Test annotation to mark the test method. Inside testAdd, it creates a Calculator instance, calls add(2, 3), and asserts the result equals 5 using assertEquals. This shows how JUnit runs tests and checks results, making it the standard for Java testing because it is simple, clear, and integrates well with Java projects.

Common Mistakes - 3 Pitfalls

Not using @Test annotation on test methods

Using System.out.println instead of assertions

Writing large test methods testing multiple things

Bonus Challenge

Now add data-driven testing with 3 different pairs of inputs and expected sums

Show Hint