mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
7cc1f2f98c
Closes https://github.com/flutter/flutter/issues/138501. --- It would be nice to turn this into a test-fixture, and create a better local environment. Here is how to run it locally: ```bash # The test expects you to be PWD in the `src` directory or it crashes. cd $ENGINE_SRC out/host_debug_unopt_arm64/flutter_tester \ --force-multithreading \ --disable-observatory \ --use-test-fonts \ --icu-data-file-path=out/host_debug_unopt_arm64/icudtl.dat \ --flutter-assets-dir=out/host_debug_unopt_arm64/gen/flutter/lib/ui/assets \ --disable-asset-fonts \ --enable-impeller \ out/host_debug_unopt_arm64/gen/canvas_test.dart.dill # "See" the output goldens. open out/host_debug_unopt_arm64/gen/skia_gold_canvas_test.dart ``` 
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.