Reverts: flutter/flutter#157032 Initiated by: gmackall Reason for reverting: https://github.com/flutter/flutter/pull/157032#issuecomment-2436336078 Original PR Author: gmackall Reviewed By: {reidbaker, bartekpacia} This change reverts the following previous change: I recently noticed the following log when building an app in verbose mode: ``` This Android Gradle plugin (8.1.0) was tested up to compileSdk = 33 (and compileSdkPreview = "UpsideDownCakePrivacySandbox"). You are strongly encouraged to update your project to use a newer Android Gradle plugin that has been tested with compileSdk = 35. ``` It looks like AGP would like us to use a newer AGP version if we want to use compileSdk 35 (which we do). This pr upgrades the tests, in advance of updating the templates.
external_textures
Tests external texture rendering between a native1 platform and Flutter.
Part of Flutter's API for plugins includes passing external textures, or textures
created outside of Flutter, to Flutter, typically using the Texture
widget. This is useful for plugins that render video, or for plugins that
interact with the camera.
For example:
Because external textures are created outside of Flutter, there is often subtle translation that needs to happen between the native platform and Flutter, which is hard to observe. These integration tests are designed to help catch these subtle translation issues.
How it works
- Each
lib/*_main.dartfile is a Flutter app instrumenting a test case. - There is a corresponding
test_driver/*_test.dartthat runs assertions.
To run the test cases locally, use flutter drive2:
flutter drive lib/frame_rate_main.dart --driver test_driver/frame_rate_test.dart
Tip
On CI, the test cases are run within our device lab.
See
devicelab/lib/tasks/integration_tests.dartand search forcreateExternalUiFrameRateIntegrationTest.The actual tests are run by task runners: