Why patterns improve test quality in JUnit - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a test method using JUnit 5.

JUnit

@Test
void [1]() {
    assertEquals(4, 2 + 2);
}

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

AadditionTest

BsumTest

CtestAddition

DcheckSum

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague method names like 'test1' or 'check'.

Not using the @Test annotation.

The method name additionTest clearly describes the test purpose, improving readability and test quality.

2fill in blank

medium

Complete the code to use the Arrange-Act-Assert pattern in the test.

JUnit

@Test
void testMultiply() {
    // Arrange
    int a = 3;
    int b = 5;

    // Act
    int result = a [1] b;

    // Assert
    assertEquals(15, result);
}

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

A*

B+

C-

D/

Attempts:

3 left

💡 Hint

Common Mistakes

Using addition or subtraction instead of multiplication.

Skipping the Arrange-Act-Assert structure.

The Act step performs multiplication using the * operator, matching the expected result.

3fill in blank

hard

Fix the error in the test assertion to correctly check for null.

JUnit

@Test
void testObjectIsNull() {
    Object obj = null;
    assert[1](obj);
}

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

ATrue

BEquals

CNotNull

DNull

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertNotNull when the object is null.

Using assertEquals instead of assertNull.

The assertNull method correctly asserts that obj is null, improving test accuracy.

4fill in blank

hard

Fill both blanks to use the Given-When-Then pattern in comments.

JUnit

@Test
void testDivide() {
    // [1]
    int numerator = 10;
    int denominator = 2;

    // [2]
    int result = numerator / denominator;

    assertEquals(5, result);
}

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

AGiven

BArrange

CWhen

DAct

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up Arrange/Act with Given/When.

Not using clear comments to separate test steps.

The Given comment describes the setup, and When describes the action, following the Given-When-Then pattern.

5fill in blank

hard

Fill all three blanks to create a parameterized test using JUnit 5.

JUnit

@ParameterizedTest
@ValueSource(ints = {2, 4, 6})
void testIsEven([1] number) {
    // [2]
    boolean isEven = number % 2 [3] 0;
    assertTrue(isEven);
}

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

Aint

BArrange

C==

Dboolean

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong parameter types.

Omitting comments that clarify test steps.

Using assignment '=' instead of equality '==' in condition.

The parameter int is used for numbers, the comment Arrange marks setup, and == checks equality, making the test clear and reusable.

Practice

1. Why do test patterns improve the quality of JUnit tests?

easy

A. They remove the need for assertions

B. They increase the runtime of tests significantly

C. They make tests easier to read and maintain

D. They automatically fix bugs in the code

Solution

1. Step 1: Understand the purpose of test patterns

   Test patterns organize test code to be clear and structured.

2. Step 2: Connect patterns to test quality

   Clear and maintainable tests help developers understand and update tests easily, improving quality.

3. Final Answer:

   They make tests easier to read and maintain -> Option C

4. Quick Check:

   Patterns improve readability = A [OK]

Hint: Patterns improve readability and maintenance [OK]

Common Mistakes:

• Thinking patterns increase test runtime
• Believing patterns remove assertions
• Assuming patterns fix bugs automatically

2. Which JUnit annotation is commonly used to apply the 'Arrange-Act-Assert' pattern in tests?

easy

A. @BeforeEach

B. @Test

C. @AfterAll

D. @Disabled

Solution

1. Step 1: Identify the annotation that marks test methods

   @Test marks the method where Arrange-Act-Assert steps happen.

2. Step 2: Understand other annotations' roles

   @BeforeEach runs setup before each test, @AfterAll runs after all tests, @Disabled skips tests.

3. Final Answer:

   @Test -> Option B

4. Quick Check:

   Test method annotation = D [OK]

Hint: Use @Test for main test steps [OK]

Common Mistakes:

• Confusing @BeforeEach with test method annotation
• Using @AfterAll for test logic
• Thinking @Disabled runs tests

3. Consider this JUnit test snippet using the 'Arrange-Act-Assert' pattern:

int result = calculator.add(2, 3);
assertEquals(5, result);

What will happen if the method add returns 4 instead of 5?

medium

A. The test will fail with an assertion error

B. The test will pass successfully

C. The test will throw a compilation error

D. The test will be skipped automatically

Solution

1. Step 1: Understand the assertion

   assertEquals(5, result) expects result to be 5.

2. Step 2: Analyze the returned value

   If add returns 4, the assertion fails because 4 != 5.

3. Final Answer:

   The test will fail with an assertion error -> Option A

4. Quick Check:

   Wrong result causes assertion failure = A [OK]

Hint: Assertion expects exact value; mismatch fails test [OK]

Common Mistakes:

• Assuming test passes with wrong result
• Thinking compilation error occurs
• Believing test skips on failure

4. This JUnit test uses a pattern but has an error:

@Test
public void testDivide() {
  int result = calculator.divide(10, 0);
  assertEquals(0, result);
}

What is the main problem here?

medium

A. Missing @BeforeEach annotation causes setup failure

B. assertEquals expects wrong value, test will pass incorrectly

C. Test method name is invalid

D. Division by zero causes an exception, test will error

Solution

1. Step 1: Identify the operation causing error

   Dividing by zero throws an exception in Java.

2. Step 2: Understand test behavior on exception

   Test will error because exception is not caught or expected.

3. Final Answer:

   Division by zero causes an exception, test will error -> Option D

4. Quick Check:

   Divide by zero throws exception = C [OK]

Hint: Division by zero throws error, not returns zero [OK]

Common Mistakes:

• Assuming test passes with zero result
• Thinking missing @BeforeEach causes error here
• Believing method name affects test execution

5. You want to improve your JUnit tests by applying the 'Arrange-Act-Assert' pattern consistently. Which approach best improves test quality?

hard

A. Separate setup, execution, and verification clearly in each @Test method

B. Write all test logic inside @BeforeEach methods

C. Use multiple assertions in @AfterAll methods

D. Avoid using assertions to speed up tests

Solution

1. Step 1: Understand the 'Arrange-Act-Assert' pattern

   This pattern divides tests into setup (Arrange), action (Act), and checks (Assert) within the test method.

2. Step 2: Identify best practice for test quality

   Keeping these steps clear inside each @Test method improves readability and debugging.

3. Final Answer:

   Separate setup, execution, and verification clearly in each @Test method -> Option A

4. Quick Check:

   Clear step separation in tests = B [OK]

Hint: Keep Arrange, Act, Assert steps clear inside @Test [OK]

Common Mistakes:

• Putting all logic in @BeforeEach
• Using assertions outside test methods
• Skipping assertions to save time