mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
1d766ed8d9
Rather than ask users to pass the complicated and long string `--extra-front-end-options=--dartdevc-canary,--dartdevc-module-format=ddc` we want a simpler flag to enable the new DDC module system/hot reload. Technically this flag enables the new module system, not necessarily hot reload directly. But we only expect people to use the flag to enable hot reload so I've chosen the name based on that. --------- Co-authored-by: Nate Biggs <natebiggs@google.com> |
||
|---|---|---|
| .. | ||
| test_data | ||
| chrome_test.dart | ||
| debugger_stepping_web_test.dart | ||
| expression_evaluation_web_test.dart | ||
| hot_reload_web_errors_test.dart | ||
| hot_reload_web_test.dart | ||
| hot_reload_with_asset_web_test.dart | ||
| hot_restart_web_amd_test.dart | ||
| hot_restart_web_ddc_library_bundle_test.dart | ||
| output_web_test.dart | ||
| README.md | ||
| stateless_stateful_hot_reload_web_test.dart | ||
| 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.