flutter/dev/integration_tests/README.md
Reid Baker 53e7e99c52
Warn that integration tests are not run automatically (#162626)
## 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].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] 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.
2025-02-03 22:36:41 +00:00

25 lines
800 B
Markdown

# 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:
```sh
flutter drive -t <test> --driver <driver>
```
For example:
```sh
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.