mirror of
https://github.com/flutter/flutter
synced 2024-10-12 19:23:02 +00:00
29bfb11c04
1. The platform code to show the keyboard wasn't working on certain devices. From my testing it appears to be related to when the code was firing. IMM won't show the soft input (or shows and then immediately hides it, it's hard to tell) if it's called before the Flutter UI is loaded. Change this to instead show the soft keyboard after a message from Flutter that main() has been started. 2. A text field was visible in the UI, and the test was run under a fuzzer that random tapped portions of the screen. Remove the text field so that the fuzzer can't accidentally open the keyboard on its own at a random time. 3. The keyboard was left open even after the app was closed. Also toggle the input off when the app was closed, so that this test can be ran multiple times in succession relatively hermetically. |
||
|---|---|---|
| .. | ||
| abstract_method_smoke_test | ||
| android_embedding_2 | ||
| android_host_app | ||
| android_semantics_testing | ||
| android_splash_screens | ||
| android_views | ||
| channels | ||
| codegen | ||
| external_ui | ||
| flavors | ||
| image_loading | ||
| ios_add2app | ||
| ios_host_app | ||
| ios_host_app_swift | ||
| module_host_with_custom_build | ||
| 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