flutter/dev/integration_tests/ios_add2app
Dan Field 1db5d66932
Capture JSON RPC errors that presently get swallowed (#31584)
* Update packages
* Capture JSON RPC errors that presently get swallowed
2019-04-25 08:27:00 -07:00
..
flutterapp Capture JSON RPC errors that presently get swallowed (#31584) 2019-04-25 08:27:00 -07:00
ios_add2app Remove timeout from add2app test for iOS (#28746) 2019-03-18 21:40:21 -07:00
ios_add2app.xcodeproj Remove timeout from add2app test for iOS (#28746) 2019-03-18 21:40:21 -07:00
ios_add2app.xcworkspace add2app test (#27712) 2019-02-23 09:56:27 -08:00
ios_add2appTests Remove timeout from add2app test for iOS (#28746) 2019-03-18 21:40:21 -07:00
Pods Replace flutter.io with flutter.dev (#30562) 2019-04-05 11:39:30 -07:00
.gitignore add2app test (#27712) 2019-02-23 09:56:27 -08:00
build_and_test.sh add2app test (#27712) 2019-02-23 09:56:27 -08:00
LICENSE add2app test (#27712) 2019-02-23 09:56:27 -08:00
Podfile add2app test (#27712) 2019-02-23 09:56:27 -08:00
README.md Remove timeout from add2app test for iOS (#28746) 2019-03-18 21:40:21 -07: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 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.