[flutter_tools] make local engine integration testing easier #65802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The integration tests can be configured to use a specific local engine
variant by setting the
FLUTTER_LOCAL_ENGINE
environment variable to thename of the local engine (e.g. "android_debug_unopt"). If the local engine build
requires a source path, this can be provided by setting the
FLUTTER_LOCAL_ENGINE_SRC_PATH
environment variable. This second variable is not necessary if the
flutter
andengine
checkouts are in adjacent directories.Fixes #65106