mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
64894be90a
P0 filed to restore: https://github.com/flutter/flutter/issues/169304, these tests take 20m+ on Linux docs causing timeouts. |
||
|---|---|---|
| .. | ||
| test_data | ||
| chrome_test.dart | ||
| debugger_stepping_web_test.dart | ||
| expression_evaluation_web_amd_test.dart | ||
| expression_evaluation_web_ddc_library_bundle_test.dart | ||
| hot_reload_web_errors_test.dart | ||
| hot_reload_web_test.dart | ||
| hot_reload_with_asset_web_test.dart | ||
| hot_restart_web_amd_test.dart | ||
| hot_restart_web_ddc_library_bundle_test.dart | ||
| output_web_test.dart | ||
| README.md | ||
| stateless_stateful_hot_reload_web_test.dart | ||
| vm_service_web_test.dart | ||
| web_driver_service_test.dart | ||
| web_run_chrome_test.dart | ||
| web_run_web_server_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.