tree: 09cc5b2c1047946c295ba4570c1ab24585f74e3e [path history] [tgz]
  1. test_data/
  2. background_isolate_test.dart
  3. daemon_mode_test.dart
  4. debugger_stepping_test.dart
  5. debugger_stepping_web_test.dart
  6. downgrade_upgrade_integration_test.dart
  7. expression_evaluation_test.dart
  8. flutter_attach_test.dart
  9. flutter_run_test.dart
  10. gen_l10n_test.dart
  11. hot_reload_test.dart
  12. lifetime_test.dart
  14. stateless_stateful_hot_reload_test.dart
  15. test_driver.dart
  16. test_utils.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.