Why integration tests verify component interaction in JUnit - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an integration test method that checks if two components interact correctly.

JUnit

public void testComponentInteraction() {
    ComponentA a = new ComponentA();
    ComponentB b = new ComponentB();
    a.setDependency([1]);
    boolean result = a.performAction();
    assertTrue(result);
}

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

Anew ComponentA()

Bnull

Cb

Dnew Object()

Attempts:

3 left

💡 Hint

Common Mistakes

Passing null instead of the dependent component.

Creating a new instance of the wrong component.

Passing a generic Object instead of the specific component.

The integration test verifies interaction by injecting ComponentB into ComponentA as a dependency.

2fill in blank

medium

Complete the code to assert that the interaction between components returns the expected value.

JUnit

assertEquals([1], a.performAction());

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

Anull

Bfalse

C0

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using false which indicates failure.

Using null which is not a boolean.

Using 0 which is not a boolean.

The test expects performAction() to return true when components interact correctly.

3fill in blank

hard

Fix the error in the test setup to correctly initialize the components for integration testing.

JUnit

ComponentA a = new ComponentA();
ComponentB b = [1];
a.setDependency(b);

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

Anew ComponentB()

Bnull

CComponentB()

Dnew Object()

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning null instead of an instance.

Omitting the new keyword.

Assigning a generic Object instead of the correct component.

The correct way to initialize ComponentB is by using new ComponentB().

4fill in blank

hard

Fill both blanks to complete the integration test that verifies interaction and result.

JUnit

ComponentA a = new ComponentA();
ComponentB b = [1];
a.setDependency(b);
assertEquals([2], a.performAction());

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

Anew ComponentB()

Btrue

Cfalse

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using false as expected result.

Passing null instead of a component instance.

Mixing up the order of blanks.

The test sets ComponentB as dependency and expects true from performAction().

5fill in blank

hard

Fill all three blanks to complete the integration test that sets up components, performs action, and asserts the result.

JUnit

ComponentA a = new [1]();
ComponentB b = new [2]();
a.setDependency(b);
boolean result = a.[3]();
assertTrue(result);

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

AComponentA

BComponentB

CperformAction

Dexecute

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong class names for instances.

Using a method name that does not exist.

Forgetting to assert the result.

The test creates instances of ComponentA and ComponentB, sets dependency, calls performAction(), and asserts the result.

Practice

1. Why do integration tests verify component interaction in JUnit testing?

easy

A. To measure the performance of individual components

B. To check if different parts of the system work together correctly

C. To test a single method in isolation

D. To check the syntax of the code

Solution

1. Step 1: Understand the purpose of integration tests

   Integration tests focus on verifying how multiple components interact, not just individual parts.

2. Step 2: Compare with other test types

   Unit tests check single methods, performance tests measure speed, and syntax checks are done by compilers, so these are not the focus of integration tests.

3. Final Answer:

   To check if different parts of the system work together correctly -> Option B

4. Quick Check:

   Integration tests = component interaction check [OK]

Hint: Integration tests check multiple parts working together [OK]

Common Mistakes:

• Confusing integration tests with unit tests
• Thinking integration tests check only one method
• Assuming integration tests measure performance

2. Which JUnit annotation is commonly used to write an integration test method?

easy

A. @Test

B. @BeforeEach

C. @Mock

D. @Ignore

Solution

1. Step 1: Identify the annotation for test methods

   The @Test annotation marks a method as a test method in JUnit, used for both unit and integration tests.

2. Step 2: Understand other annotations

   @BeforeEach runs setup code before each test, @Mock creates mock objects, and @Ignore skips tests; none define test methods themselves.

3. Final Answer:

   @Test -> Option A

4. Quick Check:

   @Test marks test methods [OK]

Hint: Use @Test to mark integration test methods [OK]

Common Mistakes:

• Using @BeforeEach as test method annotation
• Confusing @Mock with test method annotation
• Thinking @Ignore runs tests

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

public class ServiceIntegrationTest {
  @Test
  void testServiceAndRepoInteraction() {
    Service service = new Service(new Repository());
    String result = service.processData("input");
    assertEquals("processed: input", result);
  }
}

medium

A. Test fails due to null pointer exception

B. Test fails because assertion compares wrong values

C. Test passes because service processes input correctly

D. Test fails due to syntax error

Solution

1. Step 1: Analyze the test setup and method call

   The Service is created with a Repository, then processData is called with "input" which returns "processed: input".

2. Step 2: Check the assertion

   The assertion expects "processed: input" which matches the returned result, so the assertion will pass.

3. Final Answer:

   Test passes because service processes input correctly -> Option C

4. Quick Check:

   Expected = Actual = test passes [OK]

Hint: Match expected and actual strings in assertions [OK]

Common Mistakes:

• Assuming null pointer without checking code
• Confusing expected and actual in assertEquals
• Thinking syntax error exists in valid code

4. Identify the error in this JUnit integration test code snippet:

@Test
void testUserService() {
  UserService userService = new UserService(null);
  String name = userService.getUserName(1);
  assertEquals("Alice", name);
}

medium

A. Passing null to UserService causes NullPointerException

B. assertEquals arguments are reversed

C. Missing @BeforeEach annotation

D. Test method name is invalid

Solution

1. Step 1: Check object initialization

   UserService is created with null, likely causing a NullPointerException when getUserName is called.

2. Step 2: Review assertion and annotations

   assertEquals arguments are correct, @BeforeEach is optional, and method name is valid, so no errors there.

3. Final Answer:

   Passing null to UserService causes NullPointerException -> Option A

4. Quick Check:

   Null input causes runtime error [OK]

Hint: Check object dependencies are not null [OK]

Common Mistakes:

• Assuming assertion arguments are reversed
• Thinking @BeforeEach is mandatory for all tests
• Believing method names must follow special rules

5. In a JUnit integration test, why is it important to verify the interaction between Service and Repository components rather than testing them separately?

hard

A. Because testing components separately is not possible in JUnit

B. Because unit tests cannot test any logic inside components

C. Because integration tests run faster than unit tests

D. Because integration tests reveal issues in how components communicate and share data

Solution

1. Step 1: Understand integration test purpose

   Integration tests check if components like Service and Repository work together correctly, including data passing and method calls.

2. Step 2: Compare with unit tests and other options

   Unit tests do test logic inside components, integration tests are usually slower, and JUnit supports both separate and combined tests.

3. Final Answer:

   Because integration tests reveal issues in how components communicate and share data -> Option D

4. Quick Check:

   Integration tests = communication check [OK]

Hint: Integration tests find communication bugs between parts [OK]

Common Mistakes:

• Thinking unit tests cannot test logic
• Assuming integration tests are faster
• Believing JUnit can't test components separately