Mockito Tutorial: Learn mocking with 25 Junit Examples - Step 07: Verify calls on Mocks

The video tutorial introduces the concept of verify calls in BDD style, focusing on how to check if a specific method on a mock is called. It covers setting up a scenario to delete todos unrelated to a specific topic, testing the method using BDD, and employing verify methods in Mockito to ensure the method is called correctly. Advanced verification techniques, such as checking the number of times a method is called, are also discussed.

What is the primary purpose of a verify call in Mockito?

• To create a new mock object

• To initialize a test environment

• To check if a method returns the correct value

• To ensure a method is called on a mock

What is the main goal when implementing the delete method in the to-do service?

• To delete tasks not related to a specific string

• To retrieve all tasks

• To delete tasks related to a specific string

• To add new tasks to the list

In BDD style testing, what is the purpose of the 'then' part?

• To clean up after the test

• To set up the initial conditions

• To execute the method under test

• To verify the expected outcomes

How can you verify that a method is never called with a specific parameter in Mockito?

• By using the 'always' method

• By using the 'atLeast' method

• By using the 'never' method

• By using the 'times' method

What happens if you specify a method should be called twice, but it is only called once?

• The test will be ignored

• The test will be skipped

• The test will pass

• The test will fail

Which method allows you to specify the exact number of times a method should be called?

• exactly

• atLeast

• never

• times

Why is it important to verify side effects in unit tests?

• To reduce code complexity

• To confirm the correct methods are called

• To check the return values

• To ensure the test runs faster