As mentioned in the top-level README, this directory contains the Android-specific native code and tests for the scenario app. To run the tests, you will need to build the engine with the appropriate configuration.
For example, for the latest android build you've made locally:
dart ./testing/scenario_app/bin/run_android_tests.dart
Or for a specific, build, such as android_debug_unopt_arm64:
dart ./testing/scenario_app/bin/run_android_tests.dart --out-dir=../out/android_debug_unopt_arm64
Debugging the tests on CI is not straightforward but is being improved:
Locally (or on a temporary PR for CI), you can run the tests with the --smoke-test argument to run a single test by class name, which can be useful to verify the setup:
dart ./testing/scenario_app/bin/run_android_tests.dart --smoke-test dev.flutter.scenarios.EngineLaunchE2ETest
The result of adb logcat and screenshots taken during the test will be stored in a logs directory, which is either FLUTTER_LOGS_DIR (if set, such as on CI) or locally in out/.../scenario_app/logs.
You can then view the logs and screenshots on LUCI. For example:
.
See ci/builders/linux_android_emulator.json , and grep for run_android_tests.dart.
The following matrix of configurations is tested on the CI:
| API Version | Graphics Backend | Skia Gold | Rationale |
|---|---|---|---|
| 34 | Skia | Android 34 + Skia | Newer Android devices on Skia. |
| 34 | Impeller (OpenGLES) | Android 34 + Impeller OpenGLES | Newer Android devices on Impeller with OpenGLES. |
| 34 | Impeller (Vulkan) | Android 34 + Impeller Vulkan | Newer Android devices on Impeller. |
See Updating the Embedding Dependencies.
The generated output will be checked against a golden file (expected_golden_output.txt) to make sure all output was generated. A patch will be printed to stdout if they don't match.