IDE integration (IntelliJ, Eclipse) in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

JUnit Test Execution Result in IntelliJ

Given the following JUnit 5 test class, what will be the test execution result shown in IntelliJ's test runner after running this test?

JUnit

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

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

A Test fails with red cross and message 'expected 5 but was 6'.

B Test passes with green checkmark and message '1 test successful'.

C Test is skipped with yellow icon and message 'Test ignored'.

D Test does not run due to compilation error.

💡 Hint

Think about what the assertion is checking and the actual calculation.

The test adds 2 + 3 which equals 5, matching the expected value in assertEquals. Therefore, the test passes and IntelliJ shows a green checkmark with '1 test successful'.

❓ assertion

intermediate

Correct Assertion for Null Check in Eclipse JUnit

In Eclipse, you want to write a JUnit 5 test to verify that a method returns null. Which assertion is correct to use?

JUnit

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

public class UserServiceTest {
    @Test
    void testGetUserReturnsNull() {
        UserService service = new UserService();
        User user = service.getUser("unknown");
        // Which assertion to use here?
    }
}

A assertNull(user);

B assertEquals(null, user);

C assertTrue(user == null);

D assertNotNull(user);

💡 Hint

JUnit provides a specific assertion method for null checks.

assertNull(user) is the recommended JUnit assertion to check if an object is null. It provides clearer test reports in Eclipse and IntelliJ.

🔧 Debug

advanced

Debugging a Failing JUnit Test in IntelliJ

You run a JUnit test in IntelliJ and it fails with an AssertionError. You want to debug the test to find the problem. Which step is NOT part of the correct debugging process in IntelliJ?

A Use the 'Run' button to execute the test without breakpoints.

B Inspect variable values in the debugger when execution pauses at breakpoints.

C Step through the code line by line using the debugger controls.

D Set a breakpoint inside the test method and run the test in debug mode.

💡 Hint

Debugging requires pausing execution to inspect state.

Using the 'Run' button executes the test normally without pausing, so you cannot inspect variables or step through code. Debug mode with breakpoints is needed.

❓ framework

advanced

Configuring JUnit 5 in Eclipse for Maven Project

You have a Maven project in Eclipse and want to use JUnit 5 for testing. Which configuration step is essential to run JUnit 5 tests successfully in Eclipse?

A No configuration needed; Eclipse runs JUnit 5 tests automatically.

B Only add JUnit 4 dependency since Eclipse supports it by default.

C Manually download JUnit 5 jar and add it to the build path without pom.xml changes.

D Add the JUnit 5 dependency in the pom.xml and update the project.

💡 Hint

Maven manages dependencies via pom.xml.

JUnit 5 requires adding its dependency in pom.xml so Maven downloads it and Eclipse can run the tests. JUnit 4 dependency alone won't run JUnit 5 tests.

🧠 Conceptual

expert

Understanding Test Reports in IntelliJ for Parameterized Tests

You run a parameterized JUnit 5 test in IntelliJ with 3 different input sets. How does IntelliJ display the test results in the test runner panel?

JUnit

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;
import static org.junit.jupiter.api.Assertions.*;

public class MathTest {
    @ParameterizedTest
    @ValueSource(ints = {1, 2, 3})
    void testIsPositive(int number) {
        assertTrue(number > 0);
    }
}

A Shows one test failing if any input fails, no details on which.

B Shows 3 separate tests with no grouping, all passing.

C Shows one test with 3 sub-tests, each passing individually.

D Shows no test results because parameterized tests are unsupported.

💡 Hint

IntelliJ groups parameterized tests under one test name with sub-tests.

IntelliJ displays parameterized tests as one test with expandable sub-tests for each input, showing pass/fail status individually.

Practice

1. What is the main benefit of integrating JUnit tests with an IDE like IntelliJ or Eclipse?

easy

A. You can run and debug tests easily without using the command line.

B. You must write special code to make tests work in the IDE.

C. The IDE automatically fixes all test errors for you.

D. Tests run faster only when using the IDE integration.

Solution

1. Step 1: Understand IDE integration purpose

   IDE integration allows running and debugging tests inside the IDE without extra command line steps.

2. Step 2: Compare options to this purpose

   Only You can run and debug tests easily without using the command line. correctly states this benefit. Other options are incorrect or misleading.

3. Final Answer:

   You can run and debug tests easily without using the command line. -> Option A

4. Quick Check:

   IDE integration = easier test running [OK]

Hint: IDE integration means no command line needed for tests [OK]

Common Mistakes:

• Thinking IDE fixes test code automatically
• Believing special test code is needed for IDE
• Assuming tests run faster only in IDE

2. Which of the following is the correct way to run a JUnit test in IntelliJ IDEA?

easy

A. Right-click the test class or method and select 'Run'.

B. Manually compile the test class using javac command.

C. Open the terminal and type 'java TestClass'.

D. Drag the test file into the browser window.

Solution

1. Step 1: Identify how IntelliJ runs tests

   IntelliJ lets you run tests by right-clicking the test class or method and choosing 'Run'.

2. Step 2: Eliminate incorrect options

   Options A, B, and C are not how IntelliJ runs JUnit tests.

3. Final Answer:

   Right-click the test class or method and select 'Run'. -> Option A

4. Quick Check:

   Right-click + Run = IntelliJ test run [OK]

Hint: Right-click test and choose Run in IntelliJ [OK]

Common Mistakes:

• Trying to compile tests manually
• Running tests via java command directly
• Dragging files into unrelated apps

3. Given the following JUnit test in Eclipse, what will happen when you right-click the test method and select 'Run As > JUnit Test'?

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

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

medium

A. The test will fail and show a red bar in Eclipse.

B. The test will pass and show a green bar in Eclipse.

C. Eclipse will show a syntax error and not run the test.

D. Nothing happens because the test method is private.

Solution

1. Step 1: Analyze the test method and assertion

   The test method adds 2 + 3 and asserts it equals 5, which is true.

2. Step 2: Understand Eclipse JUnit run behavior

   Running the test in Eclipse will execute it and show a green bar for success.

3. Final Answer:

   The test will pass and show a green bar in Eclipse. -> Option B

4. Quick Check:

   Correct assertion = green bar pass [OK]

Hint: Correct assertions show green bar in Eclipse [OK]

Common Mistakes:

• Assuming test fails due to wrong assertion
• Thinking private methods run as tests
• Confusing syntax errors with runtime results

4. You try to run a JUnit test in IntelliJ but get an error saying "No tests found". What is the most likely cause?

medium

A. You ran the test using the right-click menu.

B. The test method is public and correctly annotated.

C. The test class does not have any methods annotated with @Test.

D. JUnit is not installed in the IDE.

Solution

1. Step 1: Understand the error message

   "No tests found" means IntelliJ did not detect any test methods to run.

2. Step 2: Identify common causes

   If the test class lacks methods annotated with @Test, no tests are found. Other options are either correct setups or unrelated.

3. Final Answer:

   The test class does not have any methods annotated with @Test. -> Option C

4. Quick Check:

   No @Test annotation = no tests found [OK]

Hint: Check for @Test annotation if no tests found error [OK]

Common Mistakes:

• Assuming test methods run without @Test
• Ignoring error messages
• Thinking right-click menu causes errors

5. In IntelliJ, you want to debug a failing JUnit test method. Which steps correctly describe how to start debugging the test?

hard

A. Delete the test and rewrite it to fix errors.

B. Run the test normally and wait for it to fail, then fix the code manually.

C. Open the terminal and run 'java -debug TestClass'.

D. Right-click the test method and select 'Debug'. Then use breakpoints to inspect variables.

Solution

1. Step 1: Identify how to debug tests in IntelliJ

   IntelliJ allows debugging by right-clicking the test method and choosing 'Debug'.

2. Step 2: Use breakpoints to inspect test execution

   Setting breakpoints lets you pause and check variable values during the test run.

3. Final Answer:

   Right-click the test method and select 'Debug'. Then use breakpoints to inspect variables. -> Option D

4. Quick Check:

   Right-click + Debug + breakpoints = test debugging [OK]

Hint: Right-click test and choose Debug to inspect variables [OK]

Common Mistakes:

• Running tests without debugging
• Using wrong commands in terminal
• Deleting tests instead of debugging