mirror of
https://github.com/flutter/flutter
synced 2024-09-13 05:11:45 +00:00
4a65a76279
Reland https://github.com/flutter/flutter/pull/146558, reverted in https://github.com/flutter/flutter/pull/146880 due to an outdated test result ## Original description - Update CS and googlesource.com link branches - Update GitHub /blob/ and /tree/ links Tested links manually and fixes a few broken or deprecated links Added a test that validates that `master` isn't used, except for specified repos. Part of https://github.com/flutter/flutter/issues/121564 |
||
---|---|---|
.. | ||
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.