mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
422d8d2dad
With this change the web.shard test suite runs all existing tests on all platforms with the version of the web debug builds that is the flutter tools default (does not support stateful hot reload). The linux bot configuration will also run some of the tests using the new web debug build (supports stateful hot reload). The timeout has been increased for this configuration to allow the additional tests to run to completion. The mac and windows configurations skip all tests for the new web debug builds. In the future the new build output will become the flutter tools default and the balance of where the tests tests are run will flip until the ability to opt out of the new build output is removed. This change is not ideal because we are still not fully testing all features with the two versions of the web debug builds that are available to users. If given the opportunity we should add additional bot configurations to run all the tests with the output that supports stateful hot reload. Fixes: https://github.com/flutter/flutter/issues/169304 Issue: https://github.com/flutter/flutter/issues/169634 |
||
|---|---|---|
| .. | ||
| 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.