mirror of
https://github.com/flutter/flutter.git
synced 2026-01-23 16:36:37 +08:00
2c817be69e
<!-- start_original_pr_link --> Reverts: flutter/flutter#178267 <!-- end_original_pr_link --> <!-- start_initiating_author --> Initiated by: bkonyi <!-- end_initiating_author --> <!-- start_revert_reason --> Reason for reverting: DWDS roll likely breaking Linux web_benchmarks_ddc_hot_reload, Linux web_benchmarks_ddc <!-- end_revert_reason --> <!-- start_original_pr_author --> Original PR Author: flutter-pub-roller-bot <!-- end_original_pr_author --> <!-- start_reviewers --> Reviewed By: {fluttergithubbot} <!-- end_reviewers --> <!-- start_revert_body --> This change reverts the following previous change: This PR was generated by `flutter update-packages --force-upgrade` followed by `dart dev/tools/bin/generate_gradle_lockfiles.dart --no-exclusion --no-gradle-generation` <!-- end_revert_body --> Co-authored-by: auto-submit[bot] <flutter-engprod-team@google.com>
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.