Why mock a Repository dependency in a ViewModel unit test?

WHAT THIS TESTS: The interviewer wants to know if you understand the boundary between a unit test and an integration test. Specifically they are checking whether you recognize that a ViewModel unit test should validate mapping and state logic without being slowed down or made flaky by real I/O. They also care if you know how to use a mocking library to substitute a concrete dependency with a controlled test double.

A GOOD ANSWER COVERS: A good answer hits four things in order. First, state the goal of isolation: a unit test should exercise only the class under test, so dependencies like a Repository that touch disk or network must be replaced. Second, explain control: with Mockito you can stub methods to return specific data or throw exceptions on demand, which lets you test success paths, error paths, and edge cases deterministically. Third, mention speed and determinism: real Room or Retrofit calls make tests slow and flaky, while mocked responses run in milliseconds. Fourth, describe verification: Mockito verify lets you assert that the ViewModel called the right Repository method with the right arguments, ensuring the contract between layers is respected.

COMMON WRONG ANSWERS: A common wrong answer is saying you mock only because the Repository is not implemented yet. That misses the point; you mock to isolate behavior even when the real implementation exists. Another red flag is claiming that mocking is too much boilerplate and that you should just use the real Repository with a test database. That conflates unit tests with integration tests. A third wrong pattern is mocking the ViewModel itself instead of its dependencies; the ViewModel is the system under test, so it should be instantiated with real constructor arguments while its collaborators are mocked.

LIKELY FOLLOW-UPS: The interviewer may ask how you handle coroutines or LiveData in ViewModel tests. They might also ask about the difference between mocks and fakes, or when you would choose a fake Repository over a mocked one. Another common follow-up is how to test the ViewModel when it collects a Flow from the Repository, which opens discussion on TestDispatcher and turbine.

ONE CONCRETE EXAMPLE: Suppose you have a NewsViewModel that calls newsRepository.getLatestNews(). In the unit test you create a mock of NewsRepository with Mockito. You stub the mock to return a list of two articles when getLatestNews is called. Then you instantiate the ViewModel with this mock and trigger the loading method. You assert that the ViewModel exposes a Success state containing those two articles. You also verify that the repository method was invoked exactly once. This proves the ViewModel correctly transforms repository output into UI state without ever hitting a real server or database.

Source: developer.android.com