mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
6d2792de5c
https://github.com/dart-lang/webdev/issues/2516 https://github.com/dart-lang/webdev/issues/2561 - Adds logic to emit newly compiled sources to a file that can be read by the bootstrapper. - Adds bootstrapping logic to reload scripts as needed. This involves implementing the necessary hot restart callback, fetching and processing the emitted file of newly compiled sources, cache busting, and loading the scripts onto the page. A lot of this logic is similar or identical to what we have for internal hot restart support. - Runs existing hot restart tests with the new bundle format. - Adds meta tag to run with utf-8 like in https://github.com/flutter/flutter/pull/161493. - Uses DWDS 24.3.3. ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [X] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [X] I signed the [CLA]. - [X] I listed at least one issue that this PR fixes in the description above. - [X] I updated/added relevant documentation (doc comments with `///`). - [X] I added new tests to check the change I am making, or this PR is [test-exempt]. - [X] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [ ] All existing and new tests are passing. |
||
|---|---|---|
| .. | ||
| test_data | ||
| chrome_test.dart | ||
| debugger_stepping_web_test.dart | ||
| expression_evaluation_web_test.dart | ||
| hot_restart_web_amd_test.dart | ||
| hot_restart_web_ddc_library_bundle_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.