flutter/dev/integration_tests/external_textures
auto-submit[bot] 778eaf6c1d
Reverts "Manual engine roll to 6884e83 (#150733)" (#150746)
Reverts: flutter/flutter#150733
Initiated by: gmackall
Reason for reverting: This breaks apps that use plugins that use `compileSdk` 31, some of which we use in our postsubmit (so it blocks the tree). 
Original PR Author: gmackall

Reviewed By: {jason-simmons}

This change reverts the following previous change:
Manual engine roll to https://github.com/flutter/engine/pull/53532, because the roll requires lockfile generation.
2024-06-25 01:20:29 +00:00
..
android Reverts "Manual engine roll to 6884e83 (#150733)" (#150746) 2024-06-25 01:20:29 +00:00
ios Start renaming by adding a new bringup: true as an Android emulator. (#142257) 2024-01-26 01:07:08 +00:00
lib Reverts "Reverts "Rename integration_tests/external_ui but do not touch anything else..."" (#142268) 2024-01-25 22:28:27 +00:00
test_driver Reverts "Reverts "Rename integration_tests/external_ui but do not touch anything else..."" (#142268) 2024-01-25 22:28:27 +00:00
pubspec.yaml Remove discontinued device_info and connectivity plugins from flutter_gallery, roll pub packages (#150585) 2024-06-21 23:10:24 +00:00
README.md Added missing code block language in docs (#147481) 2024-05-01 14:44:27 +00:00

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.dart file is a Flutter app instrumenting a test case.
  • There is a corresponding test_driver/*_test.dart that 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.dart and search for createExternalUiFrameRateIntegrationTest.

The actual tests are run by task runners:


  1. Only iOS and Android. ↩︎

  2. Unfortunately documentation is quite limited. See #142021. ↩︎