firka/flutter
firka/flutter
5
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
flutter/dev/integration_tests
History
Carlo Bernaschina a8aff38811 Add log to understand flakiness of commands_test (#11720) 
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
2017-08-22 09:54:51 -07:00
..
channels
Add integration test for platform interaction (#11580)
2017-08-11 10:38:12 +02:00
platform_interaction
Add integration test for platform interaction (#11580)
2017-08-11 10:38:12 +02:00
ui
Add log to understand flakiness of commands_test (#11720)
2017-08-22 09:54:51 -07:00
README.md
Integration test for channel communication (#9621)
2017-04-27 08:44:28 +02:00

README.md

Automated Flutter integration test suites. Each suite consists of a complete Flutter app and a flutter_driver specification that drives tests from the UI.

Intended for use with devicelab.