Repository testing with fakes in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the role of a fake repository in testing

In Android development, why do we use a fake repository when writing tests for our app?

A To automatically generate user interface layouts for different screen sizes.

B To replace the UI components with mock views during testing.

C To simulate data sources without relying on real databases or network calls, making tests faster and more reliable.

D To encrypt data before saving it to the device storage.

💡 Hint

Think about why tests should not depend on slow or unreliable external systems.

Fake repositories provide controlled, predictable data for tests, avoiding real network or database dependencies. This makes tests faster and more stable.

❓ ui_behavior

intermediate

Effect of fake repository on UI test behavior

When using a fake repository in UI tests, what is the expected behavior of the app's UI compared to using a real repository?

A The UI shows consistent, predictable data quickly without delays caused by network or database access.

B The UI randomly changes data to simulate network errors.

C The UI disables all buttons to prevent user interaction during tests.

D The UI automatically logs out the user after each test.

💡 Hint

Consider how fake data affects loading times and data consistency.

Fake repositories provide immediate, stable data, so the UI updates quickly and predictably during tests.

❓ lifecycle

advanced

Lifecycle impact of fake repository in ViewModel tests

In a ViewModel test using a fake repository, what lifecycle aspect must you consider to ensure LiveData updates are observed correctly?

A You must run the test on the main UI thread only.

B You need to manually call <code>onStart()</code> and <code>onStop()</code> on the ViewModel.

C You should disable the ViewModel lifecycle to prevent updates.

D You must observe LiveData on a <code>TestCoroutineDispatcher</code> or use <code>InstantTaskExecutorRule</code> to execute tasks synchronously.

💡 Hint

Think about how LiveData posts updates and how tests can observe them immediately.

Using InstantTaskExecutorRule or a test dispatcher ensures LiveData updates happen instantly in tests, avoiding asynchronous delays.

📝 Syntax

advanced

Correct fake repository implementation snippet

Which Kotlin code snippet correctly implements a simple fake repository that returns a fixed list of strings?

Android Kotlin

interface DataRepository {
  suspend fun fetchItems(): List<String>
}

class FakeDataRepository : DataRepository {
  override suspend fun fetchItems(): List<String> {
    return listOf("apple", "banana", "cherry")
  }
}

A

class FakeDataRepository : DataRepository {
  override suspend fun fetchItems(): List<String> {
    return listOf("apple", "banana", "cherry")
  }
}

B

class FakeDataRepository : DataRepository {
  override fun fetchItems(): List<String> {
    return listOf("apple", "banana", "cherry")
  }
}

C

class FakeDataRepository : DataRepository {
  fun fetchItems(): List<String> {
    return listOf("apple", "banana", "cherry")
  }
}

D

class FakeDataRepository : DataRepository {
  override suspend fun fetchItems(): String {
    return "apple, banana, cherry"
  }
}

💡 Hint

Check the function signature matches the interface exactly, including suspend and return type.

Option A correctly overrides the suspend function returning a List<String> as required by the interface.

🔧 Debug

expert

Identifying test failure cause with fake repository

You wrote a test using a fake repository, but the test fails because the ViewModel's LiveData never updates. What is the most likely cause?

A The fake repository returns an empty list instead of null.

B The test does not use <code>InstantTaskExecutorRule</code>, so LiveData updates are not observed synchronously.

C The ViewModel is not initialized before the test runs.

D The fake repository uses real network calls instead of fake data.

💡 Hint

Think about how LiveData updates are delivered in tests and what rules help with that.

Without InstantTaskExecutorRule, LiveData updates happen asynchronously and tests may miss them, causing failures.