mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
2160284af8
Developers can control the backend in the following ways: * **Do nothing**: Impeller with Vulkan is used where Vulkan is available with a fallback to Skia with OpenGL. * **In `AndroidManifest.xml`, specify `io.flutter.embedding.android.EnableImpeller` as `false`**: Skia with OpenGL is used. * **On the command line, specify `--no-enable-impeller`**: Skia with OpenGL is used. Manifest options will take priority command line options when there is a conflict. This matches iOS behavior per https://github.com/flutter/flutter/issues/124049 (closed as WAI). Fixes https://github.com/flutter/flutter/issues/149360
Engine Testing
This directory contains the infrastructure for running tests on the engine, which are most often run by Flutter's continuous integration (CI) systems.
The tests themselves are located in other directories, closer to the source for
each platform, language, and variant. For instance, macOS engine unit tests
written in objective C are located in the same directory as the source files,
but with a Test suffix added (e.g. "FlutterEngineTest.mm" holds the tests for
"FlutterEngine.mm", and they are located in the same directory).
Testing the Engine locally
If you are working on the engine, you will want to be able to run tests locally.
In order to learn the details of how do that, please consult the Flutter Wiki page on the subject.