flutter/packages/flutter_tools/test/web.shard
2022-06-24 10:14:08 -07:00
..
chrome_test.dart feat(tools): Arbitrary browser flags (closes #65575) (#104935) 2022-06-24 10:14:08 -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 migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00
hot_reload_web_test.dart migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00
output_web_test.dart migrate web integration tests to null safety (#106231) 2022-06-21 11:19:09 -07:00
README.md Move web integration tool tests to web.shard (#70226) 2020-11-11 15:42:15 -08:00
sdk_web_configuration_test.dart Provide flutter sdk kernel files to dwds launcher instead of dart ones (#103436) 2022-05-11 08:52:43 -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.