CS310
Mobile Application
Development
Flutter - Testing
Outline
● Testing In Flutter
○ Unit Tests
○ Widget Tests
○ Integration Tests
● Testing on Real Device
Why Testing?
● Ensure functionality, performance, and user satisfaction
● Catch bugs before deployment
● Maintain code quality in Flutter apps
● Goals of Testing in Flutter:
● Verify UI behavior
● Validate business logic
● Ensure app stability across devices
Testing in Flutter
● Unit Tests
● Widget Tests
● Integration Tests
Each type of test serves a different purpose and provides different levels of
coverage.
Integration tests are typically written last because they validate the interactions
between various parts of the app, including the UI, business logic, and any
dependencies like databases or APIs.
Testing in Flutter
In Flutter, you can use the flutter_test package, which is included in the Flutter
SDK, to write test cases.
To run your test case in Flutter, you can use below command:
Unit Testing
Unit testing is a fundamental practice that helps developers verify that each software unit
performs as expected.
Unit tests are typically small and fast, providing quick feedback to developers.
For unit end widget tests we will use test folder.
Arrange: Set up the variables and
conditions needed for the test.
Act: Execute the function or method
being tested.
Assert: Verify that the result matches
the expected outcome using the expect function.
Widget Testing
Widget testing, also known as component testing, involves testing individual
widgets in isolation.
Widget tests are more comprehensive than unit tests as they involve rendering
the widget tree and interacting with the widgets.
For unit tests, we use the test method to write a test case. However, for widget
tests, we use the testWidgets method.
pump method is useful when you want to invoke each frame individually.
pumpAndSettle is useful when you want to ensure that all asynchronous
operations have finished and the widget tree has settled into its final state.
Integrating Testing
Integration testing, also called end-to-end (E2E) testing, ensures that all components of
an application work together as expected.
Unlike unit and widget tests, integration tests focus on the complete flow of the app,
testing user interactions, navigation, and overall functionality in a real environment.
These tests simulate how a user would interact with the app, making them ideal for
verifying large parts or the entirety of an application. So we need to run integration
tests on physical devices or emulators to account for platform-specific behavior.
Integration tests reside in a separate directory inside your Flutter project, so create a
new directory named integration_test
Integrating Testing
IntegrationTestWidgetsFlutterBinding: Connects the integration test framework
with the app.
tap: Simulates a user tapping on a widget.
expect: Verifies that the UI updates correctly after user interactions.
find: Helps locate widgets within the widget tree. It provides several predefined
methods to find specific objects.
Resources
Flutter Testing:
https://docs.flutter.dev/testing/overview
How to test flutter app:
https://codelabs.developers.google.com/codelabs/flutter-app-testing#0
How to Run and Test Your Flutter App on Real Device:
https://medium.com/@blup-tool/how-to-run-and-test-your-flutter-app-on-a-real-
device-ef4898badca5
