Instrumented tests in Android Kotlin - UI Render Trace

Component - Instrumented tests

Instrumented tests run on a real or virtual Android device. They check how your app behaves in a real environment, including UI interactions and system integration.

Widget Tree

AndroidJUnitRunner
└── ActivityScenario
    └── ViewMatchers
        └── ViewActions
            └── ViewAssertions

The test runner starts the app activity, then uses matchers to find UI elements, performs actions on them, and finally asserts expected outcomes.

Render Trace - 5 Steps

Step 1: AndroidJUnitRunner

Step 2: ActivityScenario

Step 3: ViewMatchers

Step 4: ViewActions

Step 5: ViewAssertions

State Change - Re-render

Trigger:User action simulated by ViewActions (e.g., button click)

Before

UI element is visible but not interacted with

→

After

UI element state changes (e.g., new text appears, screen changes)

Re-renders:The affected UI components update to reflect the new state

UI Quiz - 3 Questions

What does AndroidJUnitRunner do in instrumented tests?

A Writes unit test logic

B Launches the app on a device or emulator

C Creates UI layouts

D Compiles the app code

Key Insight

Instrumented tests let you simulate real user interactions on actual devices or emulators. This helps catch UI bugs and integration issues that unit tests alone cannot find.