tree: bcd4d36aaf0395463e1fe4bce0292aeb19284997
  1. android_engine_test/
  2. android_hardware_smoke_test/
  3. android_module_host_with_custom_build_v2_embedding/
  4. android_semantics_testing/
  5. android_verified_input/
  6. android_views/
  7. channels/
  8. darwin_add2app_swiftpm/
  9. data_asset_app/
  10. data_asset_package/
  11. deferred_components_test/
  12. display_cutout_rotation/
  13. engine_integration_golden_test/
  14. external_textures/
  15. flavors/
  16. flutter_gallery/
  17. hook_user_defines/
  18. hybrid_android_views/
  19. ios_add2app_life_cycle/
  20. ios_add2app_uiscene/
  21. ios_app_with_extensions/
  22. ios_host_app/
  23. ios_host_app_swift/
  24. ios_platform_view_tests/
  25. keyboard_hot_restart/
  26. link_hook/
  27. module_host_with_custom_build/
  28. module_host_with_custom_build_v2_embedding/
  29. new_gallery/
  30. platform_interaction/
  31. pure_android_host_apps/
  32. record_use_test_app/
  33. record_use_test_package/
  34. release_smoke_test/
  35. spell_check/
  36. ui/
  37. web/
  38. web_compile_tests/
  39. web_e2e_tests/
  40. wide_gamut_test/
  41. widget_preview_scaffold/
  42. windowing_test/
  43. windows_startup_test/
  44. .gitignore
  45. 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.