You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 22, 2023. It is now read-only.
[integration_test] Recommend tests to be in integration_test/, fix example (#2986)
* [integration_test] Recommend tests to be in `integration_test/`, fix example
In this way, there is a clear distinction between integration tests that run on a device (in `integration_test/`, and widget tests that run with the flutter tester in `test/`.
Fixflutter/flutter#64690
`IntegrationTestWidgetsTestBinding` supports launching the on-device tests with
39
-
`flutter drive`. Note that the tests don't use the `FlutterDriver` API, they
40
-
use `testWidgets` instead.
39
+
Future<void> main() => integrationDriver();
40
+
```
41
41
42
-
Put the a file named `<package_name>_integration_test.dart` in the app'
43
-
`test_driver` directory:
42
+
You can also use different driver scripts to customize the behavior of the app
43
+
under test. For example, `FlutterDriver` can also be parameterized with
44
+
different [options](https://api.flutter.dev/flutter/flutter_driver/FlutterDriver/connect.html).
45
+
See the [extended driver](https://github.com/flutter/plugins/tree/master/packages/integration_test/example/test_driver/integration_test_extended_driver.dart) for an example.
0 commit comments