verify() for interaction verification in JUnit - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of verify() in interaction verification?

verify() checks if a specific method was called on a mock object during the test. It helps confirm that the expected interactions happened.

beginner

How do you use verify() to check a method was called exactly once?

Use verify(mockObject).methodName(args); to check the method was called once.

beginner

What happens if verify() fails during a test?

The test fails with an error showing that the expected method call did not happen as specified.

intermediate

How can you verify a method was never called?

Use verify(mockObject, never()).methodName(args); to check the method was not called at all.

intermediate

Explain the difference between verify() and verifyNoMoreInteractions().

verify() checks specific method calls, while verifyNoMoreInteractions() ensures no other calls happened on the mock beyond those verified.

What does verify(mock).someMethod() check in a test?

A That <code>someMethod()</code> was never called

B That <code>mock</code> is not null

C That <code>someMethod()</code> returned true

D That <code>someMethod()</code> was called on <code>mock</code> exactly once

verify() confirms the method was called once on the mock.

How do you verify a method was called exactly twice?

A verify(mock).method();

B verify(mock, once()).method();

C verify(mock, times(2)).method();

D verify(mock, never()).method();

Use times(2) with verify() to check two calls.

What is the result if verify() does not find the expected method call?

A Test passes silently

B Test fails with an error

C Test skips the verification

D Test logs a warning but passes

Missing expected calls cause test failure.

Which method verifies no other interactions happened on a mock?

A verifyNoMoreInteractions(mock);

B verify(mock);

C verify(mock, never());

D verifyZeroInteractions(mock);

verifyNoMoreInteractions() ensures no unexpected calls.

To check a method was never called, which syntax is correct?

A verify(mock, never()).method();

B verify(mock).method();

C verify(mock, times(0)).method();

D verifyNoMoreInteractions(mock);

never() explicitly checks zero calls.

Describe how verify() helps in testing interactions with mock objects.

Think about confirming what your code did with the mock.

Explain the difference between verifying a method call and verifying no more interactions.

One is about specific calls, the other about unexpected calls.

Practice

1. What is the main purpose of verify() in JUnit testing with mocks?

easy

A. To create a mock object

B. To check if a method was called on a mock object

C. To assert the return value of a method

D. To initialize test data before tests run

Solution

1. Step 1: Understand the role of verify()

   verify() is used to check interactions with mock objects, specifically if certain methods were called.

2. Step 2: Differentiate from other mock-related actions

   Creating mocks is done by mock(), asserting return values is done by assertEquals(), and initializing data is unrelated to verify().

3. Final Answer:

   To check if a method was called on a mock object -> Option B

4. Quick Check:

   verify() checks method calls = B [OK]

Hint: Remember: verify() confirms method calls on mocks [OK]

Common Mistakes:

• Confusing verify() with mock() creation
• Using verify() to check return values
• Thinking verify() initializes test data

2. Which of the following is the correct syntax to verify that method save() was called exactly once on a mock object repository?

easy

A. verify(repository).times(1).save();

B. verify(repository).save(1);

C. verify(repository, times(1)).save();

D. verify(repository).calledOnce(save());

Solution

1. Step 1: Recall correct verify() syntax

   The correct syntax uses verify(mockObject, times(n)).method() to check method call count.

2. Step 2: Match options to syntax

   verify(repository, times(1)).save(); matches the correct syntax. Options B, C, and D use invalid or non-existent methods.

3. Final Answer:

   verify(repository, times(1)).save(); -> Option C

4. Quick Check:

   verify(mock, times(1)).method() = A [OK]

Hint: Use verify(mock, times(1)).method() to check single call [OK]

Common Mistakes:

• Writing times(1) after method call
• Passing call count as method argument
• Using non-existent verify methods

3. Given the following code snippet, what will happen when the test runs?

MyService service = mock(MyService.class);
service.process();
verify(service, times(2)).process();

medium

A. Test fails because process() was called only once

B. Test passes because verify() ignores call count

C. Test fails due to syntax error in verify()

D. Test passes because process() was called twice

Solution

1. Step 1: Count method calls on mock

   The method process() is called once on service.

2. Step 2: Check verify() expectation

   The verify expects process() to be called twice (times(2)), but it was called once.

3. Final Answer:

   Test fails because process() was called only once -> Option A

4. Quick Check:

   verify times(2) but called once = D [OK]

Hint: Count actual calls before verify times(n) check [OK]

Common Mistakes:

• Assuming verify ignores call count
• Confusing times(2) with atLeast(2)
• Thinking one call satisfies times(2)

4. Identify the error in this test code snippet:

List<String> list = mock(List.class);
verify(list).add("item");
list.add("item");

medium

A. No error, code is correct

B. Missing times() argument in verify()

C. Incorrect mock creation syntax

D. verify() is called before the method call on the mock

Solution

1. Step 1: Understand verify() checks past calls

   verify() checks if a method was called before it is invoked.

2. Step 2: Check order of calls

   Here, verify() is called before list.add("item"), so no call happened yet to verify.

3. Final Answer:

   verify() is called before the method call on the mock -> Option D

4. Quick Check:

   verify() must follow method call [OK]

Hint: Always call method before verify() to check it [OK]

Common Mistakes:

• Calling verify() before method invocation
• Assuming verify() can predict future calls
• Ignoring call order in tests

5. You want to verify that a method updateStatus(String status) was called exactly once with argument "ACTIVE" on a mock userService. Which code snippet correctly achieves this?

hard

A. verify(userService, times(1)).updateStatus("ACTIVE");

B. verify(userService).updateStatus(anyString());

C. verify(userService, times(1)).updateStatus();

D. verify(userService, times(1)).updateStatus(anyString());

Solution

1. Step 1: Use verify() with times(1) for exact call count

   To check exactly one call, use times(1) in verify.

2. Step 2: Match method call with exact argument

   Pass the exact argument "ACTIVE" inside the method call in verify.

3. Step 3: Evaluate options

   verify(userService, times(1)).updateStatus("ACTIVE"); matches both call count and argument. verify(userService).updateStatus(anyString()); allows any string, not exact. verify(userService, times(1)).updateStatus(); misses argument. verify(userService, times(1)).updateStatus(anyString()); uses times(1) but anyString() matches any argument, not specifically "ACTIVE".

4. Final Answer:

   verify(userService, times(1)).updateStatus("ACTIVE"); -> Option A

5. Quick Check:

   verify with times(1) and exact arg = C [OK]

Hint: Use times(1) and exact argument in verify() [OK]

Common Mistakes:

• Using anyString() instead of exact argument
• Omitting times(1) for call count
• Calling verify() without arguments