github/flutter
7
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2025-06-03 00:51:18 +00:00
Code Issues Packages Projects Releases Wiki Activity
b98ffdc467
flutter/packages/flutter_tools/test/web.shard
History
Kishan Dhankecha 2867ac7885
Added missing code block language in docs (#147481) 
- added language for all code blocks
- replaced `bash` or `shell` with `sh` for consistency.
- added `sh` and `console` in the GitHub template link generator.
- updated test for GitHub template.
2024-05-01 14:44:27 +00:00
..
test_data Reland: Update link branches to main (#146882) 2024-04-17 13:16:33 +00:00
chrome_test.dart [tool] fallback to sigkill when closing Chromium (#135521) 2023-09-28 22:28:31 +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 Flutter Web Bootstrapping Improvements (#144434) 2024-03-12 22:41:26 +00:00
output_web_test.dart [flutter_tool] Delete skipped tests (#136364) 2023-10-11 10:24:14 -07:00
README.md Added missing code block language in docs (#147481) 2024-05-01 14:44:27 +00:00
vm_service_web_test.dart Add vmservice for android build options (#123034) 2023-04-18 18:16:09 +00: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/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.