Integration testing in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What is the output of this Flutter integration test snippet?

Consider this Flutter integration test code that taps a button and expects a text change. What will the test find after tapping the button?

Flutter

testWidgets('Button tap changes text', (WidgetTester tester) async {
  await tester.pumpWidget(MaterialApp(home: Scaffold(body: StatefulBuilder(
    builder: (context, setState) {
      String text = 'Before';
      return Column(children: [
        Text(text, key: Key('displayText')),
        ElevatedButton(
          onPressed: () => setState(() => text = 'After'),
          child: Text('Tap me'),
        ),
      ]);
    },
  )));
  expect(find.text('Before'), findsOneWidget);
  await tester.tap(find.byType(ElevatedButton));
  await tester.pump();
  expect(find.text('After'), findsOneWidget);
});

A The test fails because the text never changes from 'Before'.

B The test fails because the button is not found.

C The test throws a runtime error due to setState used incorrectly.

D The test passes because the text changes from 'Before' to 'After' after tapping.

💡 Hint

Remember how StatefulBuilder works and when the state variable is reset.

The variable 'text' is reinitialized to 'Before' every build, so setState changes a local variable that resets immediately. The text never updates to 'After'.

❓ lifecycle

intermediate

Which lifecycle method is best to initialize integration test bindings in Flutter?

In Flutter integration tests, which method should you call to ensure the test environment is ready before running tests?

A setUp() with runApp()

B tearDownAll() with runApp()

C tearDown() with IntegrationTestWidgetsFlutterBinding.ensureInitialized()

D setUpAll() with IntegrationTestWidgetsFlutterBinding.ensureInitialized()

💡 Hint

Initialization should happen once before all tests.

IntegrationTestWidgetsFlutterBinding.ensureInitialized() should be called inside setUpAll() to prepare the test environment once before all tests run.

🔧 Debug

advanced

What error does this integration test produce?

This Flutter integration test tries to find a widget by key but fails. What error will it raise?

Flutter

testWidgets('Find widget by key', (WidgetTester tester) async {
  await tester.pumpWidget(MaterialApp(home: Text('Hello')));
  expect(find.byKey(Key('missingKey')), findsOneWidget);
});

A TestFailure: Expected to find one matching node in the widget tree but found none.

B NoSuchMethodError: The method 'byKey' was called on null.

C TimeoutException: Widget not found within time limit.

D SyntaxError: Missing semicolon.

💡 Hint

Check what happens when find.byKey does not find any widget.

The test expects to find one widget with the key 'missingKey' but none exists, so it throws a TestFailure.

❓ navigation

advanced

What is the final screen shown after this integration test navigation?

Given this Flutter integration test code that taps a button to navigate, which screen is visible at the end?

Flutter

testWidgets('Navigate to second screen', (WidgetTester tester) async {
  await tester.pumpWidget(MaterialApp(
    home: Scaffold(
      body: Builder(builder: (context) {
        return ElevatedButton(
          onPressed: () => Navigator.push(context, MaterialPageRoute(builder: (_) => Scaffold(body: Center(child: Text('Second Screen'))))),
          child: Text('Go'),
        );
      }),
    ),
  ));
  await tester.tap(find.text('Go'));
  await tester.pumpAndSettle();
  expect(find.text('Second Screen'), findsOneWidget);
});

A The screen still shows the button labeled 'Go'.

B The screen shows the text 'Second Screen'.

C The test fails because Navigator.push is not awaited.

D The test throws an exception due to missing MaterialApp.

💡 Hint

pumpAndSettle waits for navigation animations to finish.

After tapping the button, Navigator.push navigates to a new screen showing 'Second Screen'. pumpAndSettle waits for the transition to complete.

🧠 Conceptual

expert

Which statement about Flutter integration testing is true?

Choose the correct statement about Flutter integration tests compared to widget tests.

A Integration tests do not support asynchronous operations and must be synchronous.

B Integration tests only test individual widgets in isolation without platform dependencies.

C Integration tests run on real devices or emulators and test the full app including platform channels.

D Integration tests cannot simulate user gestures like taps or scrolls.

💡 Hint

Think about the scope and environment of integration tests.

Integration tests run on real devices or emulators and test the entire app including platform-specific features, unlike widget tests which are more isolated.