mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() <!--
Thanks for filing a pull request!
Reviewers are typically assigned within a week of filing a request.
To learn more about code review, see our documentation on Tree Hygiene:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
-->
previous https://github.com/flutter/flutter/pull/167363
I have to factor out abstract class for RadioGroupRegistry and
RadioClient which are subclassed by RadioGroupState and RawRadio
respectively.
I have to do this because the RadioListTile that has 2 focusnode one for
listTile and one for the radio it builds. The issue is that RadioGroup's
keyboard shortcut has to tightly couples with the focus node of each
radio, but the radioListtile has to mute the radio's focusnode so it can
act as one control under keyboard shortcut
|
||
---|---|---|
.. | ||
android_engine_test | ||
android_module_host_with_custom_build_v2_embedding/app/src/main/java/io/flutter/addtoapp | ||
android_semantics_testing | ||
android_views | ||
channels | ||
deferred_components_test | ||
display_cutout_rotation | ||
external_textures | ||
flavors | ||
flutter_gallery | ||
hook_user_defines | ||
ios_add2app_life_cycle | ||
ios_app_with_extensions | ||
ios_host_app | ||
ios_host_app_swift | ||
ios_platform_view_tests | ||
keyboard_hot_restart | ||
link_hook | ||
module_host_with_custom_build/.gradle | ||
module_host_with_custom_build_v2_embedding | ||
new_gallery | ||
platform_interaction | ||
pure_android_host_apps | ||
release_smoke_test | ||
spell_check | ||
ui | ||
web | ||
web_compile_tests | ||
web_e2e_tests | ||
wide_gamut_test | ||
windows_startup_test | ||
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 -t <test> --driver <driver>
For example:
flutter drive -t lib/keyboard_resize.dart --driver test_driver/keyboard_resize_test.dart
New tests require new CI runner
Adding code to this directory will not automatically cause it to be run by any already existing ci tooling. This directory is intentinally a "choose your own adventure" piece of tooling.