Why CI integration enables continuous quality in JUnit - Automation Benefits in Action

Verify that CI integration runs tests automatically on code commit

Preconditions (3)

Step 1: Commit and push a code change to the repository

Step 2: Observe the CI pipeline triggered automatically

Step 3: Wait for the CI pipeline to run the JUnit tests

Step 4: Check the test results in the CI pipeline report

✅ Expected Result: The CI pipeline runs automatically on commit, executes all JUnit tests, and reports test results showing tests passed or failed

Automation Requirements - JUnit 5

Assertions Needed:

Verify that the test method executes and passes

Verify that the test output matches expected results

Best Practices:

Use @Test annotation for test methods

Use assertions from org.junit.jupiter.api.Assertions

Keep tests independent and repeatable

Use descriptive test method names

Automated Solution

JUnit

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

public class CalculatorTest {

    @Test
    void additionShouldReturnCorrectSum() {
        Calculator calculator = new Calculator();
        int result = calculator.add(2, 3);
        assertEquals(5, result, "2 + 3 should equal 5");
    }
}

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

This JUnit 5 test class CalculatorTest contains one test method additionShouldReturnCorrectSum. It creates a Calculator object and calls its add method with inputs 2 and 3.

The test uses assertEquals to check that the result is 5. This assertion ensures the method works correctly.

When this test is committed and pushed to a Git repository with CI configured, the CI tool will automatically run this test. The test passing confirms the code quality is maintained continuously.

We use @Test annotation to mark the test method, and clear assertion messages to explain failures if any.

Common Mistakes - 3 Pitfalls

{'mistake': 'Not using @Test annotation on test methods', 'why_bad': "JUnit will not recognize the method as a test, so it won't run automatically in CI", 'correct_approach': 'Always annotate test methods with @Test to ensure they are executed'}

Hardcoding expected results incorrectly

Writing tests that depend on external state or order

Bonus Challenge

Now add data-driven testing with 3 different input pairs for the add method

Show Hint

Practice

1. Why does integrating JUnit tests into a Continuous Integration (CI) system help maintain software quality?

easy

A. Because it slows down the development process

B. Because it allows developers to skip writing tests

C. Because tests run automatically on every code change, catching errors early

D. Because it only runs tests manually when requested

Solution

1. Step 1: Understand CI automation

   CI systems automatically run tests whenever code changes are made, ensuring immediate feedback.

2. Step 2: Recognize early error detection

   Running tests frequently helps find bugs early before they reach production.

3. Final Answer:

   Because tests run automatically on every code change, catching errors early -> Option C

4. Quick Check:

   CI auto-tests = early bug catch [OK]

Hint: CI runs tests automatically to catch bugs early [OK]

Common Mistakes:

• Thinking tests run only manually in CI
• Believing CI integration slows development
• Assuming tests are optional with CI

2. Which of the following is the correct JUnit 5 annotation to mark a method as a test that CI should run?

easy

A. @Test

B. @TestMethod

C. @RunTest

D. @Check

Solution

1. Step 1: Recall JUnit 5 test annotation

   The standard annotation to mark a test method in JUnit 5 is @Test.

2. Step 2: Verify other options

   @TestMethod, @RunTest, and @Check are not valid JUnit 5 annotations.

3. Final Answer:

   @Test -> Option A

4. Quick Check:

   JUnit test method = @Test [OK]

Hint: JUnit test methods always use @Test annotation [OK]

Common Mistakes:

• Using incorrect or made-up annotations
• Confusing JUnit 4 and 5 annotations
• Forgetting the @ symbol

3. Given this JUnit test snippet run in CI:

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

class CalculatorTest {
  @Test
  void addTest() {
    assertEquals(5, 2 + 3);
  }
}

What will be the test result when CI runs this?

medium

A. Test passes successfully

B. Test fails due to wrong assertion

C. Compilation error due to missing imports

D. Test skipped automatically

Solution

1. Step 1: Analyze the assertion

   The assertion checks if 2 + 3 equals 5, which is true.

2. Step 2: Confirm test setup

   All necessary imports and annotations are correct, so the test runs without errors.

3. Final Answer:

   Test passes successfully -> Option A

4. Quick Check:

   2+3=5 assertion passes [OK]

Hint: Check if assertion matches expected result [OK]

Common Mistakes:

• Assuming test fails without checking assertion
• Thinking imports are missing
• Believing tests skip without reason

4. A CI pipeline runs JUnit tests but reports failures even though the code is correct. Which is the most likely cause?

medium

A. Tests use assertions that always pass

B. JUnit tests are missing the @Test annotation

C. The CI system is not configured to run tests

D. The test methods are private instead of public

Solution

1. Step 1: Check test annotations

   Without @Test annotation, JUnit does not recognize methods as tests, causing failures or no tests run.

2. Step 2: Evaluate other options

   CI running tests incorrectly or private methods cause issues, but missing @Test is the most common cause of false failures.

3. Final Answer:

   JUnit tests are missing the @Test annotation -> Option B

4. Quick Check:

   Missing @Test = test not run/fail [OK]

Hint: Always add @Test to test methods [OK]

Common Mistakes:

• Assuming CI never runs tests
• Thinking private methods run as tests
• Ignoring missing annotations

5. In a CI environment, how does running JUnit tests on every pull request improve continuous quality beyond manual testing?

hard

A. It delays the release process by adding unnecessary steps

B. It allows developers to merge code without any review

C. It replaces the need for any manual testing or code review

D. It ensures all code changes are tested automatically before merging, preventing bugs from entering main code

Solution

1. Step 1: Understand CI pull request testing

   Running tests on every pull request automatically checks new code before merging.

2. Step 2: Recognize benefits over manual testing

   This automation prevents bugs from entering the main branch, improving quality continuously and reliably.

3. Final Answer:

   It ensures all code changes are tested automatically before merging, preventing bugs from entering main code -> Option D

4. Quick Check:

   Auto-test on PR = prevent buggy merges [OK]

Hint: Auto-test PRs stop bugs before merge [OK]

Common Mistakes:

• Thinking CI replaces all manual reviews
• Believing CI slows down releases
• Assuming tests run only after merging