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.

Practice

1. What is the main purpose of instrumented tests in Android development?

easy

A. To test only the backend logic without UI

B. To write unit tests that run on the local JVM

C. To run tests on real devices or emulators to check app behavior

D. To create UI layouts for the app

Solution

1. Step 1: Understand what instrumented tests do

   Instrumented tests run on actual devices or emulators to test app behavior in a real environment.

2. Step 2: Compare with other test types

   Unit tests run locally on JVM and do not test device features or UI on real devices.

3. Final Answer:

   To run tests on real devices or emulators to check app behavior -> Option C

4. Quick Check:

   Instrumented tests = run on device/emulator [OK]

Hint: Instrumented tests run on devices, not just local JVM [OK]

Common Mistakes:

• Confusing instrumented tests with unit tests
• Thinking instrumented tests only test backend logic
• Assuming instrumented tests create UI layouts

2. Which annotation is required to run an instrumented test with AndroidJUnit4?

easy

A. @RunWith(AndroidJUnit4::class)

B. @Ignore

C. @Before

D. @Test

Solution

1. Step 1: Identify the runner annotation

   Instrumented tests need the @RunWith(AndroidJUnit4::class) annotation to specify the test runner.

2. Step 2: Differentiate from other annotations

   @Test marks test methods, @Before runs setup code, @Ignore skips tests; none specify the runner.

3. Final Answer:

   @RunWith(AndroidJUnit4::class) -> Option A

4. Quick Check:

   Runner annotation = @RunWith(AndroidJUnit4::class) [OK]

Hint: Use @RunWith(AndroidJUnit4::class) to set test runner [OK]

Common Mistakes:

• Using @Test instead of @RunWith for runner
• Confusing @Before with runner annotation
• Forgetting to add any runner annotation

3. Given this instrumented test code snippet, what will be the output?

val appContext = InstrumentationRegistry.getInstrumentation().targetContext
val packageName = appContext.packageName
println(packageName)

medium

A. An empty string

B. The package name of the app under test

C. The package name of the test app

D. A runtime exception

Solution

1. Step 1: Understand InstrumentationRegistry usage

   InstrumentationRegistry.getInstrumentation().targetContext returns the context of the app under test, not the test app.

2. Step 2: Extract package name from app context

   appContext.packageName gives the package name of the app being tested, which is printed.

3. Final Answer:

   The package name of the app under test -> Option B

4. Quick Check:

   targetContext.packageName = app package [OK]

Hint: targetContext is app under test, not test app [OK]

Common Mistakes:

• Confusing targetContext with testContext
• Expecting empty string instead of package name
• Assuming runtime exception without cause

4. What is wrong with this instrumented test code?

@RunWith(AndroidJUnit4::class)
class ExampleInstrumentedTest {
  @Test
  fun useAppContext() {
    val context = InstrumentationRegistry.getContext()
    assertEquals("com.example.app", context.packageName)
  }
}

medium

A. InstrumentationRegistry.getContext() is deprecated; should use getInstrumentation().targetContext

B. Missing @Before annotation for setup

C. assertEquals syntax is incorrect

D. Missing @RunWith annotation

Solution

1. Step 1: Check InstrumentationRegistry usage

   InstrumentationRegistry.getContext() is deprecated and does not return the app context; getInstrumentation().targetContext should be used.

2. Step 2: Verify other parts of the code

   @RunWith is present, assertEquals syntax is correct, and @Before is not required here.

3. Final Answer:

   InstrumentationRegistry.getContext() is deprecated; should use getInstrumentation().targetContext -> Option A

4. Quick Check:

   Use getInstrumentation().targetContext, not getContext() [OK]

Hint: Use getInstrumentation().targetContext, not getContext() [OK]

Common Mistakes:

• Using deprecated getContext() method
• Assuming @Before is mandatory for all tests
• Thinking assertEquals syntax is wrong

5. You want to write an instrumented test that verifies a button click updates a TextView on a real device. Which steps should you follow to correctly implement this test?

hard

A. Use @RunWith(AndroidJUnit4::class), get test context, launch activity, perform click, check TextView text

B. Write a unit test with @Test, mock the button click, and check TextView text without device

C. Write a UI test without annotations, directly call button click method and check TextView

D. Use @RunWith(AndroidJUnit4::class), get app context with InstrumentationRegistry.getInstrumentation().targetContext, launch activity, perform click, check TextView text

Solution

1. Step 1: Setup instrumented test with correct runner and context

   Use @RunWith(AndroidJUnit4::class) and get app context via InstrumentationRegistry.getInstrumentation().targetContext to access real app environment.

2. Step 2: Launch activity, perform UI action, and verify result

   Launch the activity, simulate button click, and check if TextView text updates as expected on device/emulator.

3. Final Answer:

   Use @RunWith(AndroidJUnit4::class), get app context with InstrumentationRegistry.getInstrumentation().targetContext, launch activity, perform click, check TextView text -> Option D

4. Quick Check:

   Instrumented UI test = runner + app context + UI actions [OK]

Hint: Instrumented UI tests need real context and runner [OK]

Common Mistakes:

• Using test context instead of app context
• Writing unit tests for UI behavior
• Skipping @RunWith annotation