
Closes https://github.com/flutter/flutter/issues/160257. ~~This will sit on CI for a bit and give me a better idea of how much work there is to do.~~ Done! ## IMPORTANT: Do **not** revert on 1-2 isolated post-submit failures. While I've spent the last several weeks getting this passing all presubmit tests, and some integration tests I suspected might be affected, it is possible that there are 1-2 integration tests that will fail as a result of landing this PR. I'll disable the flag (`--no-explicit-package-dependencies`) if the failures look obvious enough, otherwise I'll revert.
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.