Fast Flutter Driver는 데스크톱 환경(특히 macOS)에서 Flutter 드라이버 테스트를 가속화하기 위해 설계된 툴킷입니다. 설정 및 런타임 성능을 최적화함으로써 테스트 실행 프로세스를 간소화하여 개발자가 통합 테스트를 더 효율적으로 수행할 수 있도록 합니다. 속도와 간편함을 중심으로 제작되었으며 기존의 Flutter 프로젝트와 원활하게 통합되며 개발 중 빠른 피드백을 제공합니다. 이 패키지는 데스크톱 기반의 Flutter 워크플로우에서 빠른 테스트 주기를 우선시하는 팀에게 이상적입니다.
Flutter Driver tests are being deprecated in favor of new Integration Tests.
I will continue to support this package as long it's feasible but it is recommended to start using Integration Tests.
Toolkit for running rapidly flutter driver tests on desktop/mobile.
This package simplifies the creation of Flutter Driver tests that can be run in bulk without restarting or rebuilding the application.
An example of how the toolkit works can be found in this article.
The reasoning for Desktop tests
The desktop builds are almost identical to Android/iOS builds in regard to the UI.
Running tests on a simulator/emulator are painful. This can be even worse on your CI.
Your CI is usually a dockerized Linux machine - running Linux flutter driver tests against Linux Flutter application is both fast and reliable.
This tool allows you to run your flutter driver tests much faster and more reliably than a build for a simulator/emulator.
The application flows that require Android/iOS plugins should still be run on a Simulator/Emulator or a real device.
Running also on Android/iOS
While running tests against Desktop will find the majority of bugs, it is recommended to run sometimes against actual devices. There are bugs in Dart (like implementing your generics in an invalid way) that can cause a native crash on a mobile device and work properly on the desktop.It's prudent to run fastdriver tests before every release on a mobile device.
Example
You can build and execute the example that works on any desktop system and Docker as well.
Usage
Add dev_dependency to your pubspec.yaml
dev_dependencies:fast_flutter_driver:^2.0.0
Create configuration class test_driver/generic/test_configuration.dart
This was the simplest setup of tests, next you would like to pass different application configuration so every time you run tests, they could be run with a different configuration (eg different page). To do that you need to add more properties to TestConfiguration.
A full example of how to do that can be found in the example folder.
Null Safety
The package supports building project that are migrated to null safety but until flutter driver is migrated to null safety, we need to pass the above flags to the command line tool.