mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
944d6c8fef
Unpins flutter_plugin_android_lifecycle where it is pinned. I then 1. ran `flutter update-packages --force-upgrade` (but only committed the changes within `dev/integration_tests/gradle_deprecated_settings/`, which is where it had been pinned) 2. followed by `./gradlew :generateLockfiles` from `dev/integration_tests/gradle_deprecated_settings/android/` (the lockfile was what was causing the CI dependency resolution failure, so this second step is the fix for that). See the reason it was pinned: https://github.com/flutter/flutter/pull/121847#discussion_r1124797112 followed by the PR that pinned it: https://github.com/flutter/flutter/pull/122043 Fixes https://github.com/flutter/flutter/issues/122039 |
||
|---|---|---|
| .. | ||
| abstract_method_smoke_test | ||
| android_custom_host_app | ||
| android_embedding_v2_smoke_test | ||
| android_host_app/.gradle | ||
| android_host_app_v2_embedding | ||
| android_module_host_with_custom_build_v2_embedding/app/src/main/java/io/flutter/addtoapp | ||
| android_semantics_testing | ||
| android_views | ||
| channels | ||
| deferred_components_test | ||
| external_ui | ||
| flavors | ||
| flutter_gallery | ||
| gradle_deprecated_settings | ||
| hybrid_android_views | ||
| ios_add2app_life_cycle | ||
| ios_app_with_extensions | ||
| ios_host_app | ||
| ios_host_app_swift | ||
| ios_platform_view_tests | ||
| module_host_with_custom_build/.gradle | ||
| module_host_with_custom_build_v2_embedding | ||
| non_nullable | ||
| platform_interaction | ||
| 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