tree: 4f6bb1bd15d5a7018dfa80a8ed3e5a4e41f9d2dd [path history] [tgz]
  1. android_engine_test/
  2. android_module_host_with_custom_build_v2_embedding/
  3. android_semantics_testing/
  4. android_verified_input/
  5. android_views/
  6. channels/
  7. deferred_components_test/
  8. display_cutout_rotation/
  9. external_textures/
  10. flavors/
  11. flutter_gallery/
  12. hook_user_defines/
  13. ios_add2app_life_cycle/
  14. ios_add2app_uiscene/
  15. ios_app_with_extensions/
  16. ios_host_app/
  17. ios_host_app_swift/
  18. ios_platform_view_tests/
  19. keyboard_hot_restart/
  20. link_hook/
  21. module_host_with_custom_build/
  22. module_host_with_custom_build_v2_embedding/
  23. new_gallery/
  24. platform_interaction/
  25. pure_android_host_apps/
  26. release_smoke_test/
  27. spell_check/
  28. ui/
  29. web/
  30. web_compile_tests/
  31. web_e2e_tests/
  32. wide_gamut_test/
  33. windowing_test/
  34. windows_startup_test/
  35. 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.