Integration testing in Flutter - Build, Publish & Deploy

Build & Publish - Integration testing

Performance Impact of Integration Testing

Integration tests run your app on a device or emulator to check how parts work together. They do not affect your app's runtime speed or battery use when users run the app. However, running many integration tests can take time and use memory on your development machine or CI system.

Integration tests help catch bugs early, which improves app stability and user experience, indirectly supporting smooth performance.

💻

How to Optimize Integration Testing for 60fps Rendering

Integration tests simulate user actions and app behavior but do not run during normal app use. To keep your app rendering smoothly at 60fps, focus on optimizing your app code, not the tests.

However, to speed up integration tests themselves:

• Run tests on fast emulators or real devices with good hardware.
• Limit tests to critical user flows to reduce test time.
• Use Flutter's flutter_driver or integration_test package efficiently by avoiding unnecessary waits.
• Run tests in parallel if your CI supports it.

Impact on App Bundle Size and Startup Time

Integration tests are separate from your app's release build. They do not increase your app's bundle size or affect startup time for users.

Test code and dependencies are only included in test builds, so your published app remains small and fast to start.

iOS vs Android Differences for Integration Testing

Flutter integration tests work similarly on iOS and Android, but some platform differences exist:

• iOS: Requires a real device or simulator with proper code signing and permissions for testing.
• Android: Emulators are easier to set up and run tests faster on many machines.
• Some platform-specific UI elements may behave differently, so test on both platforms to catch issues.
• Test automation tools and CI setup differ slightly due to platform security and signing requirements.

Relevant Store Review Guidelines and Requirements

Integration testing itself is not part of app store submission, but good testing helps meet store guidelines:

• Apple App Store: Ensure your app is stable and does not crash during review. Integration tests help catch crashes and UI bugs.
• Google Play Store: Similar stability requirements. Automated tests improve app quality.
• Both stores require apps to respect user privacy and permissions, which integration tests can verify.
• Store guidelines require apps to be responsive and accessible; integration tests can check UI flows for accessibility.

Your App Takes 5 Seconds to Load This Screen. What's Likely Wrong?

Possible issues causing slow screen load include:

• Heavy synchronous work blocking the UI thread.
• Loading large data or images without caching or lazy loading.
• Network calls done on the main thread without showing progress.
• Unoptimized widget rebuilds or animations.

Integration tests can help identify these by simulating user waits and checking for UI responsiveness.

Key Result

Integration testing in Flutter does not affect app runtime performance or size but is essential for catching bugs early to ensure smooth user experience. Optimize tests for speed on CI and test on both iOS and Android devices to meet store stability requirements.

Practice

1. What is the main purpose of integration testing in Flutter apps?

easy

A. To test individual functions for correctness

B. To check the app's UI design colors

C. To measure app performance under load

D. To check if different parts of the app work together correctly

Solution

1. Step 1: Understand integration testing goal

   Integration testing focuses on how different parts of the app interact and work together.

2. Step 2: Compare with other test types

   Unit tests check individual functions, performance tests check speed, and UI design tests check visuals.

3. Final Answer:

   To check if different parts of the app work together correctly -> Option D

4. Quick Check:

   Integration testing = check parts working together [OK]

Hint: Integration tests check combined parts, not single functions [OK]

Common Mistakes:

• Confusing integration testing with unit testing
• Thinking it tests only UI colors
• Mixing it up with performance testing

2. Which line correctly initializes integration testing in a Flutter test file?

easy

A. IntegrationTestWidgetsFlutterBinding.ensureInitialized();

B. WidgetsFlutterBinding.ensureInitialized();

C. IntegrationTestBinding.initialize();

D. TestWidgetsBinding.ensureInitialized();

Solution

1. Step 1: Identify the correct binding for integration tests

   The official Flutter integration test package uses IntegrationTestWidgetsFlutterBinding.ensureInitialized() to set up.

2. Step 2: Check other options for correctness

   WidgetsFlutterBinding is for widget tests, not integration tests. Others are incorrect or do not exist.

3. Final Answer:

   IntegrationTestWidgetsFlutterBinding.ensureInitialized(); -> Option A

4. Quick Check:

   Use IntegrationTestWidgetsFlutterBinding for integration tests [OK]

Hint: Use IntegrationTestWidgetsFlutterBinding.ensureInitialized() for integration tests [OK]

Common Mistakes:

• Using WidgetsFlutterBinding instead of IntegrationTestWidgetsFlutterBinding
• Misspelling the method name
• Trying to call a non-existent initialize() method

3. Given this integration test snippet, what will the test check?

final button = find.text('Tap me');
await tester.tap(button);
await tester.pumpAndSettle();
expect(find.text('Tapped!'), findsOneWidget);

medium

A. The test checks if the button is disabled

B. The button labeled 'Tapped!' is tapped and text changes to 'Tap me'

C. The button labeled 'Tap me' is tapped and text changes to 'Tapped!'

D. The test waits but does not tap any button

Solution

1. Step 1: Analyze the tap action

   The test finds a button with text 'Tap me' and taps it.

2. Step 2: Check the expected result

   After tapping and waiting for animations, it expects to find text 'Tapped!' on screen.

3. Final Answer:

   The button labeled 'Tap me' is tapped and text changes to 'Tapped!' -> Option C

4. Quick Check:

   Tap 'Tap me' button, expect 'Tapped!' text [OK]

Hint: Look for tap target text and expected text after tap [OK]

Common Mistakes:

• Confusing which text is tapped and which is expected
• Ignoring await pumpAndSettle() for UI update
• Assuming no tap happens

4. What is wrong with this integration test code snippet?

void main() {
  testWidgets('tap test', (tester) async {
    final binding = IntegrationTestWidgetsFlutterBinding.ensureInitialized();
    final button = find.text('Click');
    await tester.tap(button);
    expect(find.text('Clicked'), findsOneWidget);
  });
}

medium

A. Binding initialization should be outside testWidgets, in main() before tests

B. The find.text selector is incorrect syntax

C. Missing await before tester.tap

D. expect should be called before tap

Solution

1. Step 1: Check binding initialization placement

   IntegrationTestWidgetsFlutterBinding.ensureInitialized() should be called once before all tests, not inside testWidgets.

2. Step 2: Verify other code parts

   find.text syntax is correct, await is used before tap, and expect is correctly after tap.

3. Final Answer:

   Binding initialization should be outside testWidgets, in main() before tests -> Option A

4. Quick Check:

   Initialize binding once before tests [OK]

Hint: Initialize binding once before tests, not inside each test [OK]

Common Mistakes:

• Calling ensureInitialized inside each testWidgets
• Forgetting await before tap
• Misordering expect before tap

5. You want to write an integration test that types 'hello' into a TextField and then taps a button labeled 'Send'. Which sequence correctly performs this in Flutter integration tests?

hard

A. await tester.tap(find.text('Send')); await tester.enterText(find.byType(TextField), 'hello'); await tester.pump();

B. await tester.enterText(find.byType(TextField), 'hello'); await tester.tap(find.text('Send')); await tester.pumpAndSettle();

C. await tester.enterText(find.text('Send'), 'hello'); await tester.tap(find.byType(TextField)); await tester.pumpAndSettle();

D. await tester.tap(find.byType(TextField)); await tester.enterText(find.text('Send'), 'hello'); await tester.pump();

Solution

1. Step 1: Enter text into the TextField

   Use tester.enterText with find.byType(TextField) to type 'hello'.

2. Step 2: Tap the 'Send' button and wait for UI update

   Tap the button found by text 'Send' and call pumpAndSettle() to wait for animations.

3. Final Answer:

   await tester.enterText(find.byType(TextField), 'hello'); await tester.tap(find.text('Send')); await tester.pumpAndSettle(); -> Option B

4. Quick Check:

   Type first, then tap button, then wait [OK]

Hint: Type text first, then tap button, then wait for UI [OK]

Common Mistakes:

• Tapping button before typing text
• Using wrong finder for TextField or button
• Not waiting with pumpAndSettle after tap