mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
8373cae876
Fixes https://github.com/flutter/flutter/issues/182314 This cherry picks in 2 changes to stable - https://github.com/flutter/flutter/pull/180886 - The pub roller was busted, and the stable release missed the update - https://github.com/flutter/flutter/pull/180658 - Preceded manual pub roll, required to pass analysis with above change. This is a manual cherry pick, following https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md Around about when we created the release, the pub roller was busted. It is fixed now (https://github.com/flutter/flutter/issues/180503). Impacted Users: significant Impact Description: users cannot upgrade to the latest version Workaround: None Risk: Not sure, but the pub roll this is cherry picking landed very very close to the stable release being cut. Analysis and flutter doctor all pass. Test Coverage: For the widget scaffold change, tests are just relocated Validation steps: https://github.com/dart-lang/test/issues/2570#issue-3684439955 **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
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/dart run test test/integration.shard
You need to have downloaded the Dart SDK in your Flutter clone for this
to work. Running ../../bin/flutter will automatically download it.
Coverage exclusion
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.
Adding new test files
When adding a new test file make sure that it ends with _test.dart, or else it will not be run.