tree: 04b363cb93d9e4a3eb4b83f0e5c22cfa9b3be5e5 [path history] [tgz]
  1. test_data/
  2. analyze_size_test.dart
  3. android_plugin_example_app_build_test.dart
  4. background_isolate_test.dart
  5. break_on_framework_exceptions_test.dart
  6. build_ios_config_only_test.dart
  7. command_output_test.dart
  8. coverage_collection_test.dart
  9. daemon_mode_test.dart
  10. debugger_stepping_test.dart
  11. deferred_components_test.dart
  12. deprecated_gradle_settings_test.dart
  13. downgrade_upgrade_integration_test.dart
  14. expression_evaluation_test.dart
  15. flutter_attach_test.dart
  16. flutter_build_with_compilation_error_test.dart
  17. flutter_gen_test.dart
  18. flutter_run_test.dart
  19. flutter_run_with_error_test.dart
  20. forbidden_imports_test.dart
  21. gen_l10n_test.dart
  22. generated_plugin_registrant_test.dart
  23. gradle_non_android_plugin_test.dart
  24. hot_reload_errors_test.dart
  25. hot_reload_test.dart
  26. hot_reload_with_asset_test.dart
  27. ios_content_validation_test.dart
  28. lifetime_test.dart
  29. macos_content_validation_test.dart
  30. observatory_port_test.dart
  31. overall_experience_test.dart
  32. plist_parser_test.dart
  33. README.md
  34. single_widget_reload_test.dart
  35. stateless_stateful_hot_reload_test.dart
  36. template_manifest_test.dart
  37. test_driver.dart
  38. test_test.dart
  39. test_utils.dart
  40. timeline_test.dart
  41. tool_backend_test.dart
  42. unit_coverage_test.dart
  43. vmservice_integration_test.dart
  44. xcode_backend_test.dart
packages/flutter_tools/test/integration.shard/README.md

Integration tests

These tests are not hermetic, and use the actual Flutter SDK. While they don't require actual devices, they run flutter_tester to test Dart VM and Flutter integration.

Use this command to run (from the flutter_tools directory):

../../bin/cache/dart-sdk/bin/pub run test test/integration.shard

You need to have downloaded the Dart SDK in your Flutter clone for this to work. Running ../../bin/flutter will automatically download it.

Coverage exclusion

These tests are expensive to run and do not give meaningful coverage information for the flutter tool (since they are black-box tests that run the tool as a subprocess, rather than being unit tests). For this reason, they are in a separate shard when running on continuous integration and are not run when calculating coverage.