Mockito Tutorial: Learn mocking with 25 Junit Examples - Step 03: Stubbing Example - with Disadvantages of Stubbing

The video tutorial introduces the concept of stubs in unit testing, explaining how to create and use them to test a ToDo business implementation. It covers the process of creating a stub, using it in tests, and the limitations of stubs, such as maintenance challenges and dynamic condition handling. The tutorial concludes by suggesting the use of mocks as a more dynamic alternative to stubs.

What is a stub in the context of unit testing?

• A type of database

• A sample implementation used for testing

• A real implementation of a service

• A user interface component

Why do we create a stub for the to-do service?

• To improve the user interface

• To replace the main code

• To enhance database performance

• To test the to-do business implementation

What is the first step in setting up a unit test using a stub?

• Create a to-do business implementation

• Write a user manual

• Create a new database

• Implement a user interface

What is the purpose of using assert equals in a unit test?

• To create a new stub

• To check if the test runs

• To verify the expected and actual values

• To delete unnecessary code

What exercise is suggested to improve the test?

• Add more stubs

• Check the exact values in the list

• Create a new user interface

• Optimize the database

What is a major limitation of using stubs?

• They are too dynamic

• They require constant maintenance

• They are expensive

• They are too fast

What happens when a new method is added to the interface?

• The stub needs to be manually updated

• The test fails

• The database crashes

• The stub automatically updates

Why might stubs become complex over time?

• They are not used often

• They require additional logic for different scenarios

• They are too expensive

• They are too simple

What is introduced as a more dynamic alternative to stubs?

• Real implementations

• User interfaces

• Databases

• Mocks

What is the main focus of the next step after using stubs?

• Optimizing the database

• Improving the user interface

• Creating more stubs

• Introducing mocks