mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
d6d2e89fc8
Log the details of how Chromium is about to be launched prior to running the Chromium command, as well as the path to the Chromium executable. This should improve our understanding of what's happening here: https://github.com/flutter/flutter/issues/132654#issuecomment-1726630123 |
||
|---|---|---|
| .. | ||
| test_data | ||
| chrome_test.dart | ||
| debugger_stepping_web_test.dart | ||
| expression_evaluation_web_test.dart | ||
| hot_reload_web_test.dart | ||
| output_web_test.dart | ||
| README.md | ||
| vm_service_web_test.dart | ||
| web_driver_service_test.dart | ||
| 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.