mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() There have been some more additional reports of a missing 'package:characters' import after upgrading flutter. This has me concerned that our pub caching logic is incorrect. Instead of the tool attempting to guess when pub should be run, always delegate to pub. Also takes an opportunity to fix the kernel snapshot depending on the .packages or package_config. Due to the generated: date field this causes extra rebuilds. Instead when pub get is run, write out an additional file with just the package contents and version. Fixes #66777 Fixes #65723 |
||
---|---|---|
.. | ||
test_data | ||
analyze_size_test.dart | ||
background_isolate_test.dart | ||
build_ios_config_only_test.dart | ||
command_output_test.dart | ||
coverage_collection_test.dart | ||
daemon_mode_test.dart | ||
debugger_stepping_test.dart | ||
debugger_stepping_web_test.dart | ||
deprecated_gradle_settings_test.dart | ||
downgrade_upgrade_integration_test.dart | ||
expression_evaluation_test.dart | ||
expression_evaluation_web_test.dart | ||
flutter_attach_test.dart | ||
flutter_gen_test.dart | ||
flutter_immediately_exit_test.dart | ||
flutter_run_test.dart | ||
flutter_run_with_error_test.dart | ||
forbidden_imports_test.dart | ||
gen_l10n_test.dart | ||
hot_reload_errors_test.dart | ||
hot_reload_test.dart | ||
hot_reload_with_asset_test.dart | ||
lifetime_test.dart | ||
plist_parser_test.dart | ||
README.md | ||
single_widget_reload_test.dart | ||
stateless_stateful_hot_reload_test.dart | ||
template_manifest_test.dart | ||
test_driver.dart | ||
test_test.dart | ||
test_utils.dart | ||
unit_coverage_test.dart | ||
vmservice_integration_test.dart | ||
web_run_test.dart | ||
xcode_backend_test.dart |
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 VM and Flutter integration.
Use this command to run (from the flutter_tools
directory):
../../bin/cache/dart-sdk/bin/pub run test test/integration.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.