firka/flutter
firka/flutter
4
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
flutter/packages/flutter_tools/test/web.shard
History
Pascal Welsch 25c2c22d29
Delete Chrome temp cache after closing (#119062) 
* Delete Chrome temp cache after closeing

* Update packages/flutter_tools/lib/src/web/chrome.dart

Co-authored-by: Christopher Fujino <fujino@google.com>

---------

Co-authored-by: Christopher Fujino <fujino@google.com>
2023-02-10 17:39:58 +00: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
Delete Chrome temp cache after closing (#119062)
2023-02-10 17:39:58 +00: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
Move web integration tool tests to web.shard (#70226)
2020-11-11 15:42:15 -08:00
sdk_web_configuration_test.dart
Manual pub roll with dwds fix (#119575)
2023-02-02 21:38:08 +00: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

README.md

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.