ViewModel testing in Android Kotlin - Build, Publish & Deploy

Build & Publish - ViewModel testing

Performance Impact of ViewModel Testing

Testing ViewModels does not affect your app's runtime performance directly. However, well-tested ViewModels help prevent bugs that could cause UI freezes or crashes, improving user experience and app stability.

Efficient ViewModel tests run quickly and use minimal memory, enabling fast feedback during development without slowing down your workflow.

💻

Optimizing ViewModel Testing for Smooth Development

Use lightweight testing frameworks like JUnit and Mockito to keep tests fast and isolated.

Mock dependencies to avoid slow operations like network or database calls during tests.

Run tests on the JVM instead of on-device to speed up execution and reduce resource use.

Keep tests focused on one behavior to make debugging easier and maintain a 60fps development flow.

Impact on App Bundle Size and Startup Time

ViewModel testing code is not included in the app bundle shipped to users, so it does not increase app size or startup time.

Keeping test code separate ensures your release APK or AAB remains small and fast to start.

iOS vs Android Differences in ViewModel Testing

Android uses ViewModel from Jetpack libraries, which is tested with JVM unit tests using Kotlin.

iOS uses different patterns like ViewControllers or SwiftUI ViewModels, tested with XCTest.

Android ViewModel tests focus on lifecycle-aware data handling, which is unique compared to iOS.

Store Review Guidelines and Requirements

Testing ViewModels helps ensure your app meets stability and performance guidelines required by Google Play and Apple App Store.

While tests are not submitted, they reduce the chance of crashes or bugs that cause app rejection.

Follow best practices for privacy and data handling in ViewModels to comply with store policies.

Self-Check: Your App Takes 5 Seconds to Load This Screen. What's Likely Wrong?

Possible causes include heavy operations running on the main thread inside the ViewModel or UI.

Lack of proper testing might have missed slow data loading or blocking calls.

Optimize by moving work off the main thread and adding tests to catch slow operations early.

Key Result

Testing ViewModels ensures app stability without impacting runtime performance or app size. Use fast, isolated JVM tests with mocks to optimize development speed and catch bugs early, meeting store quality standards.

Practice

1.

What is the main purpose of testing a ViewModel in Android development?

easy

A. To validate user input directly on the screen

B. To verify the data handling and business logic without UI involvement

C. To test the navigation between different screens

D. To check the layout and visual appearance of the app

Solution

1. Step 1: Understand ViewModel role

   The ViewModel holds and manages UI-related data but does not handle UI rendering.

2. Step 2: Identify testing focus

   Testing ViewModel focuses on data logic and state management, not UI or navigation.

3. Final Answer:

   To verify the data handling and business logic without UI involvement -> Option B

4. Quick Check:

   ViewModel testing = data logic check [OK]

Hint: ViewModel tests focus on data, not UI or navigation [OK]

Common Mistakes:

• Confusing ViewModel testing with UI testing
• Thinking ViewModel tests check screen layouts
• Assuming navigation is tested in ViewModel tests

2.

Which annotation is commonly used to set up a ViewModel instance before each test method runs?

easy

A. @Ignore

B. @Test

C. @After

D. @Before

Solution

1. Step 1: Recall JUnit lifecycle annotations

   @Before runs before each test method to prepare test environment.

2. Step 2: Match annotation to ViewModel setup

   Use @Before to initialize ViewModel before tests run.

3. Final Answer:

   @Before -> Option D

4. Quick Check:

   Setup before tests = @Before [OK]

Hint: Use @Before to prepare ViewModel before each test [OK]

Common Mistakes:

• Using @Test instead of @Before for setup
• Confusing @After with setup annotation
• Skipping setup annotation entirely

3.

Given the following test code snippet, what will be the value of result after running the test?

class MyViewModelTest {
  private lateinit var viewModel: MyViewModel

  @Before
  fun setup() {
    viewModel = MyViewModel()
  }

  @Test
  fun testIncrement() {
    viewModel.increment()
    val result = viewModel.counter
  }
}

Assuming counter starts at 0 and increment() adds 1.

medium

A. 1

B. 0

C. null

D. Throws an exception

Solution

1. Step 1: Understand initial state

   ViewModel's counter starts at 0 before increment.

2. Step 2: Apply increment method

   Calling increment() adds 1, so counter becomes 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Initial 0 + 1 increment = 1 [OK]

Hint: Increment adds 1 to counter starting at 0 [OK]

Common Mistakes:

• Assuming counter remains 0 after increment
• Thinking result is null without initialization
• Expecting an exception without error in code

4.

Identify the error in this ViewModel test code snippet:

class SampleViewModelTest {
  private lateinit var viewModel: SampleViewModel

  @Test
  fun testReset() {
    viewModel.reset()
    assertEquals(0, viewModel.counter)
  }
}

Assuming viewModel is not initialized anywhere else.

medium

A. Missing @Before setup to initialize viewModel before test

B. Incorrect assertEquals parameter order

C. reset() method does not exist in ViewModel

D. Test method missing @Test annotation

Solution

1. Step 1: Check viewModel initialization

   viewModel is declared but never initialized before test runs.

2. Step 2: Identify missing setup

   Without @Before method to initialize viewModel, calling reset() causes error.

3. Final Answer:

   Missing @Before setup to initialize viewModel before test -> Option A

4. Quick Check:

   Initialize viewModel before test = @Before needed [OK]

Hint: Always initialize ViewModel before tests with @Before [OK]

Common Mistakes:

• Forgetting to initialize viewModel before use
• Mixing assertEquals parameter order
• Assuming reset() method is missing without checking

5.

You want to test a ViewModel method that fetches data asynchronously and updates a LiveData property. Which approach is best to test this behavior?

hard

A. Mock the LiveData property and verify it was called

B. Call the method and immediately check LiveData value without waiting

C. Use a coroutine test rule to run suspend functions and observe LiveData changes synchronously

D. Test only the UI observing the LiveData, not the ViewModel method

Solution

1. Step 1: Understand asynchronous data fetching

   ViewModel uses coroutines to fetch data and update LiveData asynchronously.

2. Step 2: Use coroutine test tools

   Coroutine test rules allow running suspend functions in tests synchronously for reliable assertions.

3. Step 3: Observe LiveData changes properly

   Observing LiveData synchronously ensures test waits for updates before asserting values.

4. Final Answer:

   Use a coroutine test rule to run suspend functions and observe LiveData changes synchronously -> Option C

5. Quick Check:

   Async ViewModel test = coroutine test rule + LiveData observe [OK]

Hint: Use coroutine test rule to handle async LiveData updates [OK]

Common Mistakes:

• Checking LiveData immediately without waiting
• Mocking LiveData instead of testing real updates
• Testing UI instead of ViewModel logic