How do you run integration tests on devices?

Integration tests run the full app, including plugins and real navigation. They catch problems that widget tests cannot, but they are slower and more environment-dependent. A good suite covers a few critical journeys rather than every screen.

void main() {
  IntegrationTestWidgetsFlutterBinding.ensureInitialized();

  testWidgets('login and open orders', (tester) async {
    await tester.pumpWidget(const App());
    await tester.enterText(find.byKey(const Key('email')), 'qa@example.com');
    await tester.enterText(find.byKey(const Key('password')), 'secret123');
    await tester.tap(find.byKey(const Key('login')));
    await tester.pumpAndSettle();

    expect(find.text('Orders'), findsOneWidget);
  });
}

• Use a dedicated test account and reset backend state before each run
• Stub or sandbox third-party services so tests do not depend on live data
• Prefer accessibility keys over visible text for stable finders
• Capture screenshots and logs on failure for diagnosis
• Run on a small device matrix, not every model, to control cost and time

Reducing flakiness

Flakiness usually comes from timing, shared backend state or real network conditions. Replace arbitrary delays with condition-based waits. Make test data unique per run. If a journey needs a push notification or permission dialog, handle the platform prompt explicitly or exclude that path from the automated suite and test it manually.