mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() - Update CS and googlesource.com link branches - Update GitHub /blob/ and /tree/ links Tested links manually and fixes a few broken or deprecated links Added a test that validates that `master` isn't used, except for specified repos. Part of https://github.com/flutter/flutter/issues/121564 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/wiki/Tree-hygiene#overview [Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene [test-exempt]: https://github.com/flutter/flutter/wiki/Tree-hygiene#tests [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [Features we expect every widget to implement]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/wiki/Chat [Data Driven Fixes]: https://github.com/flutter/flutter/wiki/Data-driven-Fixes |
||
---|---|---|
.. | ||
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_verified_input | ||
android_views | ||
channels | ||
deferred_components_test | ||
external_textures | ||
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 | ||
new_gallery | ||
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