flutter/packages/flutter_tools/test/web.shard
2022-09-06 11:05:41 -07:00
..
test_data [tool] Fix flutter.js regression with hot-reload on promise-based init. (#110805) 2022-09-01 22:25:16 +00:00
chrome_test.dart [flutter_tools] Pull more arm64 artifacts on Apple Silicon (#110291) 2022-08-29 10:33:24 -07:00
debugger_stepping_web_test.dart migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00
expression_evaluation_web_test.dart Temporarily remove a bogus warning until fixed by dwds update (#109793) 2022-08-19 11:06:53 -07:00
hot_reload_web_test.dart Update issue reference for skipped hot restart tests (#110881) 2022-09-02 14:38:24 -07:00
output_web_test.dart migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00
README.md
sdk_web_configuration_test.dart Migrate packages/flutter_tools/test/web.shard (#110713) 2022-09-06 11:05:41 -07:00
vm_service_web_test.dart migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00
web_driver_service_test.dart migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00
web_run_test.dart migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00

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/pub 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.