mirror of https://github.com/flutter/flutter.git synced 2026-02-20 02:29:02 +08:00

History

Move explicit package dependencies to a feature flag (#158016 )

Closes https://github.com/flutter/flutter/issues/158012.

This is (effectively) a user-facing NOP, which is exchanging an
on-by-default command-line argument (`--implicit-pubspec-resolution`)
for an off-by-default global feature flag
(`explicit-package-dependencies`). It matches the mental model better,
is less painstaking to maintain and feed throughout, and will be easier
to globally flip on/off in a future PR.

---------

Co-authored-by: Andrew Kolos <andrewrkolos@gmail.com>

2024-11-13 18:33:34 -08:00

test_data

Migrate apple-mobile-web-* to mobile-web-*. (#154964 )

2024-09-11 00:39:51 +00:00

chrome_test.dart

fix test chrome.close can recover if getTab throws a StateError (#154889 )

2024-09-10 17:23:56 +00:00

debugger_stepping_web_test.dart

…

expression_evaluation_web_test.dart

…

hot_reload_web_test.dart

Flutter Web Bootstrapping Improvements (#144434 )

2024-03-12 22:41:26 +00:00

output_web_test.dart

…

README.md

Added missing code block language in docs (#147481 )

2024-05-01 14:44:27 +00:00

vm_service_web_test.dart

…

web_driver_service_test.dart

Move explicit package dependencies to a feature flag (#158016 )

2024-11-13 18:33:34 -08:00

web_run_test.dart

…

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.