Why test structure ensures clarity in JUnit - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a test method in JUnit 5.

JUnit

@[1]
public void testAddition() {
    int sum = 2 + 3;
    assertEquals(5, sum);
}

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

ATest

BBeforeEach

CAfterEach

DIgnore

Attempts:

3 left

💡 Hint

Common Mistakes

Using lifecycle annotations like @BeforeEach instead of @Test.

Forgetting the @Test annotation.

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

2fill in blank

medium

Complete the code to assert that two strings are equal in a JUnit test.

JUnit

assert[1]("hello", greeting);

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

ANull

BTrue

CEquals

DSame

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertTrue instead of assertEquals for equality.

Mixing up expected and actual parameters.

The assertEquals method checks if two values are equal in JUnit tests.

3fill in blank

hard

Fix the error in the test method declaration by completing the annotation.

JUnit

@org.junit.jupiter.api.[1]
void checkValue() {
    assertTrue(value > 0);
}

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

ABeforeAll

BDisabled

CAfterAll

DTest

Attempts:

3 left

💡 Hint

Common Mistakes

Using lifecycle annotations like @BeforeAll or @AfterAll instead of @Test.

Missing the annotation entirely.

The correct annotation to mark a test method is @Test from JUnit Jupiter API.

4fill in blank

hard

Fill both blanks to create a test method that checks if a list is empty.

JUnit

@[1]
public void testListEmpty() {
    List<String> list = new ArrayList<>();
    assert[2](list.isEmpty());
}

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

ATest

BTrue

CFalse

DBeforeEach

Attempts:

3 left

💡 Hint

Common Mistakes

Using @BeforeEach instead of @Test.

Using assertFalse instead of assertTrue for checking empty list.

The method must be annotated with @Test and use assertTrue to check if the list is empty.

5fill in blank

hard

Fill all three blanks to write a test that verifies a string contains a substring.

JUnit

@[1]
public void testContains() {
    String text = "JUnit testing";
    assert[2](text.[3]("test"));
}

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

ATest

BTrue

Ccontains

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertFalse instead of assertTrue.

Using wrong method name instead of contains.

The test method uses @Test annotation, asserts true for the condition, and calls contains on the string.

Practice

1. Why is using a clear test structure important in JUnit testing?

easy

A. It increases the runtime of tests.

B. It reduces the number of tests needed.

C. It automatically fixes bugs in the code.

D. It makes tests easier to read and understand.

Solution

1. Step 1: Understand the purpose of test structure

   A clear test structure helps anyone reading the test to quickly understand what is being tested and how.

2. Step 2: Relate clarity to test maintenance

   When tests are easy to read, developers can find and fix bugs faster, improving code quality.

3. Final Answer:

   It makes tests easier to read and understand. -> Option D

4. Quick Check:

   Clear structure = better readability [OK]

Hint: Clear tests = easy to read and fix bugs fast [OK]

Common Mistakes:

• Thinking test structure reduces test count
• Believing tests fix bugs automatically
• Assuming test structure slows tests

2. Which of the following is the correct order of the Arrange-Act-Assert pattern in a JUnit test?

easy

A. Act, Arrange, Assert

B. Assert, Act, Arrange

C. Arrange, Act, Assert

D. Arrange, Assert, Act

Solution

1. Step 1: Recall the Arrange-Act-Assert pattern

   Arrange means setting up test data or environment, Act means executing the code under test, Assert means checking the results.

2. Step 2: Confirm the correct sequence

   The logical flow is first prepare (Arrange), then perform action (Act), then verify outcome (Assert).

3. Final Answer:

   Arrange, Act, Assert -> Option C

4. Quick Check:

   Arrange before Act, then Assert [OK]

Hint: Remember AAA: Arrange, Act, Assert order [OK]

Common Mistakes:

• Mixing up the order of steps
• Asserting before acting
• Arranging after acting

3. Consider this JUnit test snippet:

 @Test
 void testSum() {
   int a = 2;
   int b = 3;
   int result = a + b;
   assertEquals(5, result);
 }

What will be the test result when run?

medium

A. Test passes successfully

B. Test fails due to wrong assertion

C. Test throws a compilation error

D. Test is skipped automatically

Solution

1. Step 1: Analyze the test code logic

   The test adds 2 and 3, stores in result, then asserts result equals 5.

2. Step 2: Check assertion correctness

   Since 2 + 3 equals 5, the assertion assertEquals(5, result) will pass.

3. Final Answer:

   Test passes successfully -> Option A

4. Quick Check:

   2 + 3 = 5, assertion true [OK]

Hint: Check math and assertion values carefully [OK]

Common Mistakes:

• Assuming assertion fails without checking values
• Confusing compilation errors with runtime failures
• Thinking tests skip without @Ignore

4. Identify the error in this JUnit test method:

 @Test
 void testMultiply() {
   int a = 4;
   int b = 5;
   int result = a * b
   assertEquals(20, result);
 }

medium

A. Missing semicolon after multiplication assignment

B. Incorrect expected value in assertEquals

C. Test method missing @Before annotation

D. Using assertEquals with wrong parameter order

Solution

1. Step 1: Check syntax line by line

   The line 'int result = a * b' is missing a semicolon at the end, causing a syntax error.

2. Step 2: Verify assertion and annotations

   The expected value 20 is correct for 4*5, and @Test annotation is present, so no other errors.

3. Final Answer:

   Missing semicolon after multiplication assignment -> Option A

4. Quick Check:

   Every statement needs a semicolon [OK]

Hint: Look for missing semicolons in code lines [OK]

Common Mistakes:

• Ignoring missing semicolon errors
• Assuming wrong assertEquals parameters
• Confusing @Before with @Test

5. You want to write a clear JUnit test for a method that returns the maximum of two numbers. Which test structure best ensures clarity and maintainability?

hard

A. Combine setup, execution, and assertion in one line without comments

B. Use Arrange-Act-Assert pattern with descriptive variable names and comments

C. Write only assertions without setup or execution steps

D. Write multiple assertions without separating test steps

Solution

1. Step 1: Understand best practices for test clarity

   Using the Arrange-Act-Assert pattern separates test steps clearly, making tests easier to read and maintain.

2. Step 2: Importance of descriptive names and comments

   Descriptive variable names and comments help others understand the test purpose quickly.

3. Final Answer:

   Use Arrange-Act-Assert pattern with descriptive variable names and comments -> Option B

4. Quick Check:

   AAA pattern + clear names = clarity [OK]

Hint: Follow AAA pattern with clear names and comments [OK]

Common Mistakes:

• Writing all steps in one line
• Skipping setup or execution steps
• Mixing multiple assertions without structure