mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
b65ff54de2
The keyboard hot restart test listens to `flutter run` logs and then does an action. However, the test prints the `flutter run` log after the action. This results in confusing logs. For example: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8716606099574306145/+/u/run_keyboard_hot_restart_ios/stdout ``` ═══════════╡ ••• Launch app and wait for keyboard to be visible ••• ╞═══════════ ... stdout: Installing and launching... 37.2s stdout: Syncing files to device swarming’s iPhone... ════╡ ••• Update the app to no longer force the keyboard to be visible ••• ╞════ ════════════════════════╡ ••• Hot restart the app ••• ╞═════════════════════════ ════════════╡ ••• Wait until the keyboard is no longer visible ••• ╞════════════ stdout: flutter: Keyboard is open ``` Here, the test waits until the keyboard is visible before moving onto the test's next step. However, the log that triggers this action (`flutter: Keyboard is open`) is printed after the action was taken (`Update the app to no longer force the keyboard to be visible` and `Wait until the keyboard is no longer visible`). This is confusing. Follow-up to: https://github.com/flutter/flutter/pull/167013 Part of: https://github.com/flutter/flutter/issues/10713 |
||
|---|---|---|
| .. | ||
| analysis.dart | ||
| android_choreographer_do_frame_test.dart | ||
| android_lifecycles_test.dart | ||
| android_views_test.dart | ||
| build_test_task.dart | ||
| dart_plugin_registry_tests.dart | ||
| entrypoint_dart_registrant.dart | ||
| flutter_tool_startup.dart | ||
| gallery.dart | ||
| hot_mode_tests.dart | ||
| integration_tests.dart | ||
| keyboard_hot_restart_test.dart | ||
| microbenchmarks.dart | ||
| native_assets_test.dart | ||
| new_gallery.dart | ||
| perf_tests.dart | ||
| platform_channels_benchmarks.dart | ||
| plugin_tests.dart | ||
| run_tests.dart | ||
| web_benchmarks.dart | ||
| web_dev_mode_tests.dart | ||