tree: a2daf9aec414f36f43ac7729a213318eb0460ff2 [path history] [tgz]
  1. android/
  2. ios/
  3. lib/
  4. .gitignore
  6. pubspec.yaml

Scenario App

This folder contains e2e integration tests for the engine in conjunction with a fake dart:ui framework running in JIT or AOT.

It intentionally has no dependencies on the Flutter framework or tooling, such that it should be buildable as a presubmit or postsubmit to the engine even in the face of changes to Dart or dart:ui that require upstream changes in the Flutter tooling.

Adding a New Scenario

Create a new subclass of Scenario and add it to the map in scenarios.dart. For an example, see animated_color_square.dart, which draws a continuously animating colored square that bounces off the sides of the viewport.

Then set the scenario from the Android or iOS app by calling “set_scenario” on platform channel.

Running for iOS

Build the ios_debug_sim_unopt engine variant, and run


in your shell.

To run or debug in Xcode, open the xcodeproj file located in <engine_out_dir>/scenario_app/Scenarios/Scenaios.xoceproj.

iOS Platform View Tests

For PlatformView tests on iOS, you‘ll also have to edit the dictionaries in AppDelegate.m and GoldenTestManager.m so that the correct golden image can be found. Also, you’ll have to add a GoldenPlatformViewTests in PlatformViewUITests.m.

If PlatformViewRotation is failing, make sure Simulator app Device > Rotate Device Automatically is selected, or run:

defaults write RotateWindowWhenSignaledByGuest -int 1

Generating Golden Images on iOS

Screenshots are saved as XCTAttachment‘s. If you look at the output from running the tests you’ll find a path in the form: /Users/$USER/Library/Developer/Xcode/DerivedData/Scenarios-$HASH. Inside that directory you'll find ./Build/Products/Debug-iphonesimulator/ which is where all the images that were compared against golden reside.

Running for Android

The only test that is currently run is the Firebase TestLab test, which is a smoke test to make sure an application can be built and run on a real Android device.

To run it, build the android_profile_arm64 variant of the engine, and run ./flutter/ci/ If you wish to test a different variant, e.g. debug arm64, pass --variant android_debug_arm64.

Updating Gradle dependencies

If a Gradle dependency is updated, lockfiles must be regenerated.

To generate new lockfiles, run:

cd android
../../../../gradle/bin/gradle generateLockfiles