All 7 Integration Testing in Flutter questions
More in Integration Testing in Flutter
What is the integration_test package, and how does it let you actually run your Flutter integration tests directly on a real physical device or a properly configured emulator? How does pumpAndSettle differ from a single simple pump call within an integration test, and why is it genuinely so commonly and frequently used specifically after triggering an action that starts an animation or a network request? How do you properly simulate genuinely realistic user gestures, such as scrolling, dragging, and long pressing, within an integration test using the WidgetTester's own available gesture methods? How should you properly and correctly handle actual external dependencies, such as a genuine real network API or Firebase, within an integration test, given that these tests genuinely run using your actual real complete app? How do you properly and correctly measure and profile genuine real world performance metrics, such as actual frame rendering time, directly from within an integration test using Flutter's own dedicated performance testing tools?
Advertisement
Back to results for “CI/CD”
Flutter › Integration Testing in Flutter

How can integration tests genuinely be properly integrated into a CI/CD pipeline, given that they genuinely require an actual real device or emulator to actually run, unlike considerably simpler and faster unit tests?

Advanced

Answer

Running integration tests within a CI/CD pipeline genuinely requires access to an actual real device or a properly configured emulator, which typically means using a cloud based device farm service, such as Firebase Test Lab, or properly configuring your own CI runner to actually spin up a genuine emulator instance itself, and since integration tests genuinely run considerably slower than unit tests, many teams choose to only actually run their full integration test suite on specific key branches, such as their main branch or before a genuine actual release, rather than genuinely running the entire suite on every single individual pull request the exact same way they would with their considerably faster unit tests.
# GitHub Actions step running integration tests via Firebase Test Lab
- run: gcloud firebase test android run --type instrumentation --app app.apk
Real-world example A team configures their CI pipeline to run their full integration test suite using Firebase Test Lab specifically before every single production release, while still continuing to run their considerably faster unit and widget tests on every single individual pull request as usual.

Common follow-ups: What are the genuine cost implications of regularly and repeatedly running integration tests against a genuine cloud based device farm service?;How do you actually properly and correctly parallelize a genuinely large integration test suite to actually meaningfully reduce its own overall total run time?

CI/CD Pipelines for Flutter Apps;Unit Testing in Flutter
All 7 Integration Testing in Flutter questions