tree: e4437cbbf7f05644547c17d4073cb42e2bb3af94 [path history] [tgz]
  1. android_engine_test/
  2. android_module_host_with_custom_build_v2_embedding/
  3. android_semantics_testing/
  4. android_views/
  5. channels/
  6. deferred_components_test/
  7. display_cutout_rotation/
  8. external_textures/
  9. flavors/
  10. flutter_gallery/
  11. hook_user_defines/
  12. ios_add2app_life_cycle/
  13. ios_app_with_extensions/
  14. ios_host_app/
  15. ios_host_app_swift/
  16. ios_platform_view_tests/
  17. keyboard_hot_restart/
  18. link_hook/
  19. module_host_with_custom_build/
  20. module_host_with_custom_build_v2_embedding/
  21. new_gallery/
  22. platform_interaction/
  23. pure_android_host_apps/
  24. release_smoke_test/
  25. spell_check/
  26. ui/
  27. web/
  28. web_compile_tests/
  29. web_e2e_tests/
  30. wide_gamut_test/
  31. windows_startup_test/
  32. README.md
dev/integration_tests/README.md

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.