flutter/dev/integration_tests/ui
Greg Spencer 2aad59314f
Add a keyboard key code generator. (#27620)
This adds a keycode generator that incorporates input from the Chromium and Android source trees, as well as some local tables, to generate static constants for the LogicalKeyboardKey and PhysicalKeyboardKey classes, as well as mappings from each of the platforms we support so far (currently only Android and Fuchsia).

This code generator parses the input files, generates an intermediate data structure (`key_data.json`) that is checked in, and then generates the Dart sources for these classes and some static maps that will also be checked in (but are not included in this PR).

The idea is that these codes don't change often, and so we don't need to generate them on every build, but we would like to be able to update them easily in the future if new data becomes available. If the existing data disappears or becomes unusable, we can maintain the checked-in data structure by hand if necessary, and still be able to generate the code.

This PR only contains the code generator, not the classes themselves. In another follow-on PR, I'll run the generator and check in the output of the generator.
2019-02-06 16:53:16 -08:00
..
android Revert "Upgrade the Gradle script to Android plugin version 3.3.0 (#26913)" (#27045) 2019-01-24 14:29:08 -08:00
ios Roll engine to 05fee4eeee0ff6b219b1fcc394371e5f6963cc46 (#26713) 2019-01-21 21:23:04 -08:00
lib Make a kReleaseMode constant that is public. (#27502) 2019-02-06 14:37:17 -08:00
test_driver Revert "Update driver script to execute test through test_core" (#24401) 2018-11-15 11:17:00 -08:00
pubspec.yaml Add a keyboard key code generator. (#27620) 2019-02-06 16:53:16 -08:00
README.md Deep linking: automatically push the route hiearchy on load. (#10894) 2017-06-23 14:58:29 -07:00

Flutter UI integration tests

This project contains a collection of non-plugin-dependent UI integration tests. The device code is in the lib/ directory, the driver code is in the test_driver/ directory. They work together. Normally they are run via the devicelab.

keyboard_resize

Verifies that showing and hiding the keyboard resizes the content.

routing

Verifies that flutter drive --route works correctly.