flutter/dev/integration_tests/ios_add2app
Ben Konyi 3edd3eb4a2
Updated package:test, package:test_core, package:coverage, package:package_config (#51946)
This is required to roll forward package:vm_service to 3.0.0 and is
blocking a DevTools release.
2020-03-04 11:40:52 -08:00
..
flutterapp Updated package:test, package:test_core, package:coverage, package:package_config (#51946) 2020-03-04 11:40:52 -08:00
ios_add2app License update (#45373) 2019-11-27 15:04:02 -08:00
ios_add2app.xcodeproj Turn on bitcode for integration tests and add-to-app templates (#44633) 2019-11-12 18:00:31 -08:00
ios_add2app.xcworkspace add2app test (#27712) 2019-02-23 09:56:27 -08:00
ios_add2appTests License update (#45373) 2019-11-27 15:04:02 -08:00
.gitignore Remove ios_add2app Pods directory and add to gitignore (#33772) 2019-06-03 14:27:10 -07:00
build_and_test.sh Revert "Revert "Add many more global analyses. (#47875)" (#48080)" (#48081) 2020-01-02 11:47:28 -08:00
Podfile Remove use_modular_headers from Podfiles using libraries (#42872) 2019-10-17 15:26:10 -07:00
README.md Simple repeating word fixes (#51871) 2020-03-03 11:13:07 -08:00

iOS Add2App Test

This application demonstrates some basic functionality for Add2App, along with a native iOS ViewController as a baseline and to demonstrate interaction.

The following functionality is currently implemented:

  1. A regular iOS view controller (UIViewController), similar to the default flutter create template (NativeViewController.m).
  2. A FlutterViewController subclass that takes over full screen. Demos showing this both from a cold/fresh engine state and a warm engine state (FullScreenViewController.m).
  3. A demo of pushing a FlutterViewController on as a child view.
  4. A demo of showing both the native and the Flutter views using a platform channel to interact with each other (HybridViewController.m).
  5. A demo of showing two FlutterViewControllers simultaneously (DualViewController.m).

A few key things are tested here (IntegrationTests.m):

  1. The ability to pre-warm the engine and attach/detatch a ViewController from it.
  2. The ability to use platform channels to communicate between views.
  3. The ability to simultaneously run two instances of the engine.
  4. That a FlutterViewController can be freed when no longer in use (also tested from FlutterViewControllerTests.m).
  5. That a FlutterEngine can be freed when no longer in use.