mirror of
https://github.com/flutter/flutter
synced 2024-10-13 19:52:53 +00:00
2d623278e7
This moves the app template more toward being a more generic starting point for any Flutter application, eliminating some hard-code assumptions about there being a single window/engine pair that is directly bound to the life of the application: - Moves the runloop into its own class, making it capable of servicing any number of engine instances. - Moves the logic for setting up a window containing only a Flutter view into a window subclass for ease of re-use. - Makes quit-on-window-close an optional property. (Long term this should be even more generic, like a quit-when-last-window-closes option, but this is a short-term improvement that removes the binding between the runloop and the window). - Allows for multiple instances of Win32Window to exist without issues relating to the window class registration. Since there are getting to be a non-trivial number of files associated with the runner, this moves the source into a runner/ directory, as is already done on some other platforms. Note that creating multiple Flutter windows at the same time still doesn't work correctly even with this change, but this addresses some of the known issues, and makes it easier to test in the future (e.g., for debugging engine-level issues with multiple instances). Fixes #45397 |
||
|---|---|---|
| .. | ||
| abstract_method_smoke_test | ||
| android_custom_host_app | ||
| android_embedding_v2_smoke_test | ||
| android_host_app | ||
| android_host_app_v2_embedding | ||
| android_module_host_with_custom_build_v2_embedding/app/src/main/java/io/flutter/addtoapp | ||
| android_semantics_testing | ||
| android_splash_screens | ||
| android_views | ||
| channels | ||
| codegen | ||
| external_ui | ||
| flavors | ||
| flutter_driver_screenshot_test | ||
| flutter_gallery | ||
| image_loading | ||
| ios_add2app | ||
| ios_add2app_life_cycle | ||
| ios_host_app | ||
| ios_host_app_swift | ||
| ios_platform_view_tests | ||
| module_host_with_custom_build | ||
| module_host_with_custom_build_v2_embedding | ||
| named_isolates | ||
| platform_interaction | ||
| release_smoke_test | ||
| simple_codegen | ||
| ui | ||
| web | ||
| web_compile_tests | ||
| README.md | ||
Automated Flutter integration test suites. Each suite consists of either a
complete Flutter app and a flutter_driver specification that drives tests
from the UI, or a native app that is meant to integrate with Flutter for
testing.
Intended for use with devicelab tests.
If you want to run a driver test locally, to debug a problem with a test, you can use this command from the appropriate subdirectory:
% flutter drive