tree: aa10ec9a8f2aa2dc34eecfd2aa10336ef4c4a040 [path history] [tgz]
  1. test_data/
  2. chrome_test.dart
  3. debugger_stepping_web_test.dart
  4. expression_evaluation_web_test.dart
  5. hot_reload_web_test.dart
  6. output_web_test.dart
  8. vm_service_web_test.dart
  9. web_driver_service_test.dart
  10. web_run_test.dart

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.