tree: daf4a4de957e3134c255269a96e288de340d6be0 [path history] [tgz]
  1. abstract_method_smoke_test/
  2. android_custom_host_app/
  3. android_embedding_v2_smoke_test/
  4. android_host_app/
  5. android_host_app_v2_embedding/
  6. android_module_host_with_custom_build_v2_embedding/
  7. android_semantics_testing/
  8. android_verified_input/
  9. android_views/
  10. channels/
  11. deferred_components_test/
  12. external_textures/
  13. flavors/
  14. flutter_gallery/
  15. gradle_deprecated_settings/
  16. hybrid_android_views/
  17. ios_add2app_life_cycle/
  18. ios_app_with_extensions/
  19. ios_host_app/
  20. ios_host_app_swift/
  21. ios_platform_view_tests/
  22. module_host_with_custom_build/
  23. module_host_with_custom_build_v2_embedding/
  24. new_gallery/
  25. non_nullable/
  26. platform_interaction/
  27. release_smoke_test/
  28. spell_check/
  29. ui/
  30. web/
  31. web_compile_tests/
  32. web_e2e_tests/
  33. wide_gamut_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