tree: 2a3007619762d628a03bff6b6450100577d8e3a1 [path history] [tgz]
  1. test_data/
  2. analyze_size_test.dart
  3. background_isolate_test.dart
  4. build_ios_config_only_test.dart
  5. command_output_test.dart
  6. coverage_collection_test.dart
  7. daemon_mode_test.dart
  8. debugger_stepping_test.dart
  9. debugger_stepping_web_test.dart
  10. deprecated_gradle_settings_test.dart
  11. downgrade_upgrade_integration_test.dart
  12. expression_evaluation_test.dart
  13. expression_evaluation_web_test.dart
  14. flutter_attach_test.dart
  15. flutter_gen_test.dart
  16. flutter_run_test.dart
  17. flutter_run_with_error_test.dart
  18. forbidden_imports_test.dart
  19. gen_l10n_test.dart
  20. hot_reload_test.dart
  21. lifetime_test.dart
  22. plist_parser_test.dart
  24. stateless_stateful_hot_reload_test.dart
  25. template_manifest_test.dart
  26. test_driver.dart
  27. test_utils.dart
  28. unit_coverage_test.dart
  29. vmservice_integration_test.dart
  30. web_run_test.dart
  31. xcode_backend_test.dart

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

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.