launching-activities-with-activityscenario

To migrate from ActivityTestRule to ActivityScenario, use ActivityScenarioRule with the canonical FQN androidx.test.ext.junit.rules.ActivityScenarioRule to launch Activities safely and ensure proper lifecycle-aware teardown.

You can test Android lifecycle transitions using ActivityScenario by calling moveToState to drive an Activity through CREATED, STARTED, RESUMED, or DESTROYED states, verifying behavior at each lifecycle phase.

To interact with UI views safely without deadlocks in ActivityScenario tests, use the onActivity block to execute view mutations and state reads on the UI thread, avoiding direct scenario API calls from the main thread.

To simulate configuration changes and test state restoration, call recreate on your ActivityScenario to trigger state save and restore flows, verifying that rememberSaveable, SavedStateHandle, and onSaveInstanceState survive the process.

You can assert results from an Activity launched with launchActivityForResult by accessing scenario.result, which captures the returned Intent data and result code for robust instrumentation test assertions.

ActivityScenario tests fail with main thread deadlocks when scenario APIs are incorrectly called from the UI thread; prevent this by wrapping interactions in onActivity and ensuring proper cleanup via close or the JUnit rule.