Why CI integration enables continuous quality in JUnit - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does CI integration improve software quality?

Continuous Integration (CI) is a key practice in modern software development. Which of the following best explains why CI integration enables continuous quality?

A CI allows developers to write code without testing, relying on manual checks later.

B CI runs automated tests on every code change, catching bugs early and preventing faulty code from merging.

C CI integration delays testing until the end of the development cycle to save time.

D CI only checks code formatting and ignores functional tests.

💡 Hint

Think about how frequent testing affects bug detection.

CI runs automated tests on every code change, which helps find bugs early. This prevents bad code from being merged and keeps the software quality high continuously.

❓ Predict Output

intermediate

JUnit test result in CI pipeline

Consider this JUnit test class run in a CI pipeline. What will be the test execution result?

JUnit

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

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

    @Test
    void testSubtract() {
        int result = 5 - 3;
        assertEquals(1, result);
    }
}

A One test fails, one test passes.

B Both tests pass successfully.

C Both tests fail due to assertion errors.

D Tests do not run because of syntax errors.

💡 Hint

Check the expected values in assertions carefully.

The first test checks if 2 + 3 equals 5, which passes. The second test expects 5 - 3 to be 1, but 5 - 3 is 2, so this test fails.

❓ assertion

advanced

Correct assertion for CI test to verify list size

In a CI pipeline, you want to assert that a list returned by a method has exactly 3 items. Which JUnit assertion is correct?

JUnit

import static org.junit.jupiter.api.Assertions.assertEquals;
import java.util.List;

List<String> items = List.of("a", "b", "c");

A assertEquals(3, items.size());

B assertEquals(items, 3);

C assertEquals(3, items);

D assertEquals(items.size(), 3);

💡 Hint

Remember the order of expected and actual values in assertEquals.

assertEquals expects the first argument as the expected value and the second as the actual value. items.size() returns an int, so comparing it to 3 is correct.

🔧 Debug

advanced

Identify the cause of test failure in CI

Given this JUnit test run in CI, why does it fail?

JUnit

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

public class SampleTest {
    @Test
    void testCondition() {
        boolean condition = (5 > 10);
        assertTrue(condition);
    }
}

A The test fails because the method is missing @BeforeEach annotation.

B The test fails due to a syntax error in the code.

C The test fails because assertTrue requires a string argument.

D The assertion fails because 5 is not greater than 10.

💡 Hint

Check the boolean condition used in assertTrue.

The condition (5 > 10) is false, so assertTrue fails and the test fails in CI.

❓ framework

expert

Why does CI integration with JUnit improve feedback speed?

In a CI environment using JUnit tests, what is the main reason this setup improves feedback speed for developers?

A CI integration with JUnit only runs tests once a week, slowing feedback.

B JUnit tests require manual triggering, so feedback is delayed until testers run them.

C JUnit tests run automatically on each commit, providing immediate pass/fail results to developers.

D JUnit tests in CI ignore failed tests to avoid blocking developers.

💡 Hint

Think about how automation affects developer awareness of issues.

CI runs JUnit tests automatically on every code commit, so developers get quick feedback on whether their changes broke anything, enabling fast fixes and continuous quality.