Why advanced sources handle complex data in JUnit - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a basic JUnit test method.

JUnit

public class CalculatorTest {
    @Test
    public void testAddition() {
        Calculator calc = new Calculator();
        int result = calc.add(2, 3);
        assertEquals([1], result);
    }
}

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

A6

B7

C4

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong expected value in assertEquals.

Forgetting to import the @Test annotation.

The expected result of adding 2 and 3 is 5, so assertEquals(5, result) is correct.

2fill in blank

medium

Complete the code to assert that a list contains a specific element.

JUnit

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

public class ListTest {
    @Test
    public void testContainsElement() {
        List<String> fruits = List.of("apple", "banana", "cherry");
        assertTrue(fruits.[1]("banana"));
    }
}

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

Aincludes

Bexists

Ccontains

Dhas

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods that do not exist on List, like 'has' or 'exists'.

Confusing the method name with similar words.

The contains method checks if the list has the specified element.

3fill in blank

hard

Fix the error in the assertion to correctly compare two objects for equality.

JUnit

public class PersonTest {
    @Test
    public void testPersonEquality() {
        Person p1 = new Person("Alice", 30);
        Person p2 = new Person("Alice", 30);
        assert[1](p1, p2);
    }
}

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

AEquals

BSame

CEqualTo

DEqualsObject

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertSame instead of assertEquals for object equality.

Using non-existent assertion methods.

The correct JUnit assertion method to check object equality is assertEquals.

4fill in blank

hard

Fill both blanks to create a parameterized test method that runs with multiple inputs.

JUnit

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;

public class NumberTest {
    @ParameterizedTest
    @ValueSource([1])
    public void testIsPositive(int number) {
        assertTrue(number [2] 0);
    }
}

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

Aints = {1, 2, 3}

B{1, 2, 3}

C>

D>=

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the type attribute (e.g., ints =) in @ValueSource.

Using >= instead of >, which would accept zero as positive.

The @ValueSource annotation requires a type-specific attribute such as ints = {1, 2, 3} for integer values. The assertion uses > to verify the number is positive (greater than zero).

5fill in blank

hard

Fill all three blanks to write a test that verifies a map contains a key with a specific value.

JUnit

import static org.junit.jupiter.api.Assertions.*;
import java.util.Map;

public class MapTest {
    @Test
    public void testMapKeyValue() {
        Map<String, Integer> ages = Map.of("Bob", 25, "Carol", 30);
        assertTrue(ages.[1]("Bob") && ages.get("Bob") [2] [3]);
    }
}

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

AcontainsKey

B==

C25

Dequals

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' to compare Integer objects which may fail.

Using a method other than containsKey to check for keys.

The method containsKey checks if the map has the key. To compare the value, equals is used to compare with 25.

Practice

1. Why do advanced test sources handle complex data like nested maps or JSON strings in JUnit tests?

easy

A. Because JUnit only supports complex data types

B. Because simple data types are faster to test

C. To reduce the number of test cases needed

D. To simulate real-world scenarios and verify detailed behaviors

Solution

1. Step 1: Understand the purpose of complex data in tests

   Complex data like nested maps or JSON strings represent real-world data structures more accurately than simple types.

2. Step 2: Connect complex data to test accuracy

   Using complex data helps verify that the system handles all parts of the data correctly, ensuring realistic test coverage.

3. Final Answer:

   To simulate real-world scenarios and verify detailed behaviors -> Option D

4. Quick Check:

   Complex data tests real scenarios = D [OK]

Hint: Real data needs complex structures to test well [OK]

Common Mistakes:

• Thinking simple data is always enough
• Believing JUnit only supports complex types
• Assuming fewer test cases means better tests

2. Which of the following is the correct way to declare a nested Map in a JUnit test source for complex data?

easy

A. Map> data = new HashMap<>();

B. Map data = new HashMap<>(); data.put(new HashMap<>(), 'value');

C. Map data = new HashMap();

D. Map data = new Map();

Solution

1. Step 1: Check syntax for nested Map declaration

   Map> data = new HashMap<>(); correctly declares a Map with String keys and Map values using HashMap.

2. Step 2: Identify errors in other options

   Map data = new HashMap<>(); data.put(new HashMap<>(), 'value'); tries to put a Map as a key, which is invalid here; Map data = new HashMap(); uses List instead of Map; Map data = new Map(); uses invalid syntax for Map instantiation.

3. Final Answer:

   Map> data = new HashMap<>(); -> Option A

4. Quick Check:

   Correct nested Map syntax = B [OK]

Hint: Nested Map needs correct generic types and HashMap instantiation [OK]

Common Mistakes:

• Using raw types without generics
• Incorrect Map instantiation syntax
• Mixing List and Map types incorrectly

3. Given the following JUnit test snippet, what will be the assertion result?

Map data = Map.of(
  "user", Map.of("name", "Alice", "age", 30),
  "active", true
);
assertEquals("Alice", ((Map)data.get("user")).get("name"));

medium

A. Test fails because 'name' key is missing

B. Test passes because the name is 'Alice'

C. Test fails because of a ClassCastException

D. Test fails because 'active' is not a Map

Solution

1. Step 1: Analyze the data structure

   The 'data' map contains a key 'user' with a nested Map value holding 'name' and 'age'.

2. Step 2: Evaluate the assertion

   The assertion extracts the nested Map for 'user' and gets the 'name' value, which is 'Alice', matching the expected value.

3. Final Answer:

   Test passes because the name is 'Alice' -> Option B

4. Quick Check:

   Nested Map access returns 'Alice' = C [OK]

Hint: Cast nested map before accessing keys [OK]

Common Mistakes:

• Forgetting to cast Object to Map
• Assuming keys are missing
• Confusing keys at different levels

4. Identify the error in this JUnit test code handling complex data:

Map data = new HashMap<>();
data.put("info", Map.of("id", 101, "status", "active"));
assertEquals(101, data.get("info").get("id"));

medium

A. assertEquals expects two strings, but got int and Object

B. Map.of cannot be used inside a HashMap

C. Cannot call get("id") on Object without casting

D. Keys 'id' and 'status' must be integers

Solution

1. Step 1: Analyze the data retrieval

   data.get("info") returns an Object, which must be cast to Map to call get("id") on it.

2. Step 2: Identify the error in assertion

   Without casting, calling get("id") on Object causes a compile-time error.

3. Final Answer:

   Cannot call get("id") on Object without casting -> Option C

4. Quick Check:

   Cast Object to Map before get() = A [OK]

Hint: Cast Object to Map before accessing nested keys [OK]

Common Mistakes:

• Ignoring casting requirement
• Misunderstanding Map.of usage
• Wrong assertion argument types

5. You want to test a method that processes a JSON string representing a list of users, each with nested address info. Which approach best handles this complex data in JUnit tests?

hard

A. Parse JSON into nested Maps and assert each field separately

B. Test only the JSON string length to confirm input

C. Convert JSON to a flat list of strings and assert size only

D. Ignore nested data and test only top-level keys

Solution

1. Step 1: Understand the data complexity

   The JSON string contains nested user and address info, requiring detailed checks.

2. Step 2: Choose testing approach

   Parsing JSON into nested Maps allows assertions on each important field, ensuring thorough validation.

3. Final Answer:

   Parse JSON into nested Maps and assert each field separately -> Option A

4. Quick Check:

   Detailed nested assertions test complex data best = A [OK]

Hint: Parse and assert nested fields for full coverage [OK]

Common Mistakes:

• Testing only string length or flat data
• Ignoring nested fields in assertions
• Assuming top-level keys are enough