
The flakiness of commands_test is generally visible via: ``` drive:stdout: Expected: 'log: paint' drive:stdout: Actual: '' drive:stdout: Which: is different. Both strings start the same, but the actual value is missing the following trailing characters: log: paint ... ``` By returning the name of the test we will be able to understand if another test is running by reading the `Actual` value
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.