What problem does it solve? Compose UI tests often claim to verify state restoration but silently prove nothing: they re-read the same state instance, call the wrong setContent overload, or use plain remember which never survives a save/restore cycle. This Skill provides the canonical StateRestorationTester workflow so tests genuinely prove that rememberSaveable state survives process death and configuration change emulation. ## Core Features & Use Cases - Correct round-trip structure: Enforces constructing StateRestorationTester from a ComposeContentTestRule, calling restorationTester.setContent instead of rule.setContent, and nulling the hoisted state reference between phases so the assertion reads the post-restoration composition. - Wrong vs right patterns: Contrasts remember vs rememberSaveable, rule.setContent vs tester.setContent, and re-reading the same instance vs nulling between phases, with cited AOSP source lines. - Boundary awareness: Documents the 1 MB Bundle cap, incompatibility with createEmptyComposeRule, and what the tester does NOT cover (Activity recreation, ViewModel SavedStateHandle). - Use Case: A developer writes a regression test proving a LazyColumn scroll position survives process death; the Skill guides them to scroll to a non-default index, capture values in runOnIdle, null the state, call emulateSavedInstanceStateRestore, and assert equality. ## Quick Start Write a Compose UI test that verifies a rememberSaveable value survives a save and restore cycle using StateRestorationTester.
