tree: c7295a088b2de1ef4f6ef16ad108861133927dcd [path history] [tgz]
  1. test_data/
  2. chrome_test.dart
  3. debugger_stepping_web_test.dart
  4. expression_evaluation_web_amd_test.dart
  5. expression_evaluation_web_ddc_library_bundle_test.dart
  6. hot_reload_web_errors_test.dart
  7. hot_reload_web_test.dart
  8. hot_reload_with_asset_web_test.dart
  9. hot_restart_web_amd_test.dart
  10. hot_restart_web_ddc_library_bundle_test.dart
  11. output_web_test.dart
  12. README.md
  13. stateless_stateful_hot_reload_web_test.dart
  14. vm_service_web_test.dart
  15. web_driver_service_test.dart
  16. web_run_chrome_test.dart
  17. web_run_web_server_test.dart
packages/flutter_tools/test/web.shard/README.md

Web 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 web debug services (dwds) and Flutter integration.

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

../../bin/cache/dart-sdk/bin/dart run test test/web.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.