tree: 5460b30411d347136d34a0b2f8fb3b13bdae0771 [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_splash_screens/
  9. android_views/
  10. channels/
  11. codegen/
  12. external_ui/
  13. flavors/
  14. flutter_driver_screenshot_test/
  15. flutter_gallery/
  16. gradle_deprecated_settings/
  17. image_loading/
  18. ios_add2app/
  19. ios_add2app_life_cycle/
  20. ios_app_with_watch_companion/
  21. ios_host_app/
  22. ios_host_app_swift/
  23. ios_platform_view_tests/
  24. module_host_with_custom_build/
  25. module_host_with_custom_build_v2_embedding/
  26. named_isolates/
  27. non_nullable/
  28. platform_interaction/
  29. release_smoke_test/
  30. simple_codegen/
  31. ui/
  32. web/
  33. web_compile_tests/
  34. 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