mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
30f4fecfeb
Towards https://github.com/flutter/flutter/issues/161333. This adds the initial `.ci.yaml` configuration (marked `bringup: true`), without changing the existing shard to avoid the problems we ran into last time when I renamed the shard atomically, as well as piping for providing context in which the test will run (Vulkan or OpenGLES), which can't be introspected in the _running_ app. In a follow-up PR I'll: - Edit `AndroidManifest.xml` before the suite, setting `ImpellerBackend` appropriately - Move the bringup nodes to presubmit - Delete the existing (legacy) node
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