mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() Fixes https://github.com/flutter/flutter/issues/162615 Can test 2 different ways. On a mac (or linux machine) with adb on the path (or android sdk set in ANDROID_HOME) and an emulator running (or physical device attached) that is api 30 or higher. ``` cd dev/devicelab dart bin/test_runner.dart test -t android_display_cutout ``` OR ``` dev/integration_tests/display_cutout_rotation flutter drive integration_test/display_cutout_test.dart ``` Proof the test ran successfully ``` [2025-02-12 08:08:22.069817] [STDOUT] Removing Synthetic notch... [2025-02-12 08:08:22.071147] [STDOUT] Executing "/b/s/w/ir/cache/android/sdk/platform-tools/adb -s emulator-5554 shell cmd overlay disable com.android.internal.display.cutout.emulation.tall" in "/b/s/w/ir/x/w/rc/tmpk3k3yhhp/flutter sdk/dev/integration_tests/display_cutout_rotation/" with environment {BOT: true, LANG: en_US.UTF-8} [2025-02-12 08:08:22.862219] [STDOUT] Checking for reboot [android_defines_test] Process terminated with exit code 0. Task result: { "success": true, "data": null, "detailFiles": [], "benchmarkScoreKeys": [], "reason": "success" } ``` https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8723125792202374961/+/u/run_android_defines_test/stdout All checks passed https://github.com/flutter/flutter/pull/162641/checks?check_run_id=36991537539 ## 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. |
||
---|---|---|
.. | ||
android_engine_test | ||
android_module_host_with_custom_build_v2_embedding/app/src/main/java/io/flutter/addtoapp | ||
android_semantics_testing | ||
android_views | ||
channels | ||
deferred_components_test | ||
display_cutout_rotation | ||
external_textures | ||
flavors | ||
flutter_gallery | ||
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
New tests require new CI runner
Adding code to this directory will not automatically cause it to be run by any already existing ci tooling. This directory is intentinally a "choose your own adventure" piece of tooling.