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 main.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_and_run_ios_tests.sh

iOS Platform View Tests

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

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/ScenariosUITests-Runner.app/PlugIns/ScenariosUITests.xctest/ which is where all the images that were compared against golden reside.

Running for Android

./build_and_run_android_tests.sh

Generating Golden Images on Android

In the android directory, run:

./gradlew app:recordDebugAndroidTestScreenshotTest

The screenshots are recorded into android/reports/screenshots.

Verifying Golden Images on Android

In the android directory, run:

./gradlew app:verifyDebugAndroidTestScreenshotTest

Changing dart:ui code

If you change the dart:ui interface, remember to point the sky_engine and sky_services clauses to your local engine's output path before compiling.