What problem does it solve? Multi-screen Flutter flows involving navigation, dependency injection, and real app startup cannot be verified by unit or widget tests alone, leaving critical user journeys untested until manual QA catches failures. ## Core Features & Use Cases - Journey Test Authoring: Writes integration_test suites that boot the real app via app.main(), drive the UI with WidgetTester, and assert dynamic user-entered values rather than static labels. - Stable Selector Strategy: Adds Key-based selectors sourced from actual widget code, with a priority order of Key, find.text, then find.byType. - Device Execution & Goldens: Runs tests on emulators or physical devices with flutter test integration_test -d <device-id>, and captures device-accurate golden screenshots when needed. - Use Case: A task-management app needs proof that creating a task round-trips through the real stack. This Skill writes a journey test that taps the FAB, enters a title, saves, and asserts the new row and updated total appear on a running emulator. ## Quick Start Write and run an integration_test journey test for the create-task flow on my connected Android emulator, asserting the entered task title appears in the list.