IDE integration (IntelliJ, Eclipse) in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the JUnit test annotation.

JUnit

import org.junit.[1];

Drag options to blanks, or click blank then click option'

AIgnore

BBefore

CAfter

DTest

Attempts:

3 left

💡 Hint

Common Mistakes

Importing @Before or @After instead of @Test

Forgetting to import any annotation

The @Test annotation marks a method as a test method in JUnit.

2fill in blank

medium

Complete the code to create a test method named testAddition.

JUnit

@Test
public void [1]() {
    // test code here
}

Drag options to blanks, or click blank then click option'

AtestAddition

BadditionTest

CaddTest

DcheckAddition

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names that don't start with 'test'

Using invalid Java method names

By convention, test methods often start with 'test' followed by the feature name, like testAddition.

3fill in blank

hard

Fix the error in the assertion to check if sum equals 5.

JUnit

int sum = 2 + 3;
assertEquals([1], sum);

Drag options to blanks, or click blank then click option'

A5

Bsum

C"5"

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using the actual value as expected

Using a string instead of an integer

The expected value should be the integer 5, not the variable sum or a string.

4fill in blank

hard

Fill both blanks to import the assertion and write a failing test method.

JUnit

import static org.junit.Assert.[1];

@Test
public void testFail() {
    [2]("Failing test");
}

Drag options to blanks, or click blank then click option'

Afail

BassertTrue

DassertEquals

Attempts:

3 left

💡 Hint

Common Mistakes

Importing assertTrue but calling fail

Calling assertEquals instead of fail

The fail method from JUnit causes the test to fail immediately with a message.

5fill in blank

hard

Fill all three blanks to write a test that checks if a list contains a value.

JUnit

import static org.junit.Assert.[1];
import java.util.List;

@Test
public void testListContains() {
    List<String> items = List.of("apple", "banana", "cherry");
    boolean contains = items.contains("banana");
    [2]("List should contain banana", contains);
    [3](true, contains);
}

Drag options to blanks, or click blank then click option'

AassertTrue

BassertFalse

DassertEquals

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertFalse instead of assertTrue

Mixing up assertTrue and assertEquals

Use assertTrue to check the condition is true, and assertEquals to compare expected and actual values.

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