mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
9cc132d4c2
A few changes in this PR (could have been split up, but that would take an extra 4 hours - 2 days in CI time): - Removed the old `flutter_driver_android_test` shards and references - Override `AndroidManifest.xml` per backend, forcing that backend to be used (no fallbacks) or it fails - Bumps the Android emulator to 35 due to the use of magic strings, I think The check for the Impeller backend actually being used is the honor system right now, as a bug in `flutter drive` (https://github.com/flutter/flutter/issues/162087) prevents me from seeing error output, meaning that it's impossible to be sure a particular Impeller backend is used (or understand why a crash happens), so I guess I'll work on that next. Due to https://github.com/flutter/flutter/issues/162088, we were accidentally running our Vulkan tests as OpenGLES 🤦🏼 . |
||
|---|---|---|
| .. | ||
| android_engine_test | ||
| android_module_host_with_custom_build_v2_embedding/app/src/main/java/io/flutter/addtoapp | ||
| android_semantics_testing | ||
| android_verified_input | ||
| android_views | ||
| channels | ||
| deferred_components_test | ||
| display_cutout_rotation | ||
| external_textures | ||
| flavors | ||
| flutter_gallery | ||
| hybrid_android_views | ||
| ios_add2app_life_cycle | ||
| ios_app_with_extensions | ||
| ios_host_app | ||
| ios_host_app_swift | ||
| ios_platform_view_tests | ||
| link_hook | ||
| module_host_with_custom_build/.gradle | ||
| module_host_with_custom_build_v2_embedding | ||
| new_gallery | ||
| non_nullable | ||
| 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