launching-activities-with-activityscenario

Test Android Activity lifecycle transitions using the ActivityScenario API to drive an Activity through CREATED, STARTED, RESUMED, and DESTROYED states. This provides precise state control and ensures reliable instrumentation tests without thread-safety issues.

Emulate configuration changes to test ViewModel state restoration by calling the recreate method within ActivityScenario. This safely triggers Activity destruction and recreation, allowing you to verify saved instance state logic correctly restores the UI.

The best way to migrate from ActivityTestRule to modern Android testing is adopting ActivityScenario. It resolves migration pitfalls by providing a thread-safe environment for launching activities, managing state transitions, and synchronizing the UI thread.

Yes, you need the androidx.test.core and androidx.test.ext.junit dependencies to use ActivityScenario for Android instrumentation testing. These libraries are required to ensure canonical and thread-safe test execution during activity launching and state transitions.

Your UI state might not restore correctly after an activity configuration change if your test lacks proper lifecycle management. Using ActivityScenario's recreate method ensures the Activity is safely destroyed and recreated, accurately verifying your ViewModel and saved state logic.