History

Don't try to stop the same app twice in flutter_attach test (#20905 )

This test is sometimes flaky (#20822) because the two processes try to stop the same app. This fix changes to just gracefully terminate the attach process without explicitly trying to stop and then uses the original spawning process to stop the app.

I can't repro the flake locally to be certain, but I've verified only one stop command is sent now so it *should* be good.

2018-08-22 17:13:34 +01:00

test_data

Clean up usage of temporary directories (#20682 )

2018-08-17 13:17:23 -07:00

expression_evaluation_test.dart

Double all timeouts on flutter_tools integration tests (#20872 )

2018-08-22 17:13:23 +01:00

flutter_attach_test.dart

Don't try to stop the same app twice in flutter_attach test (#20905 )

2018-08-22 17:13:34 +01:00

flutter_tester_test.dart

Clean up usage of temporary directories (#20682 )

2018-08-17 13:17:23 -07:00

hot_reload_test.dart

Double all timeouts on flutter_tools integration tests (#20872 )

2018-08-22 17:13:23 +01:00

lifetime_test.dart

Double all timeouts on flutter_tools integration tests (#20872 )

2018-08-22 17:13:23 +01:00

README.md

Integration test for FlutterTesterDevice. (#16424 )

2018-04-11 08:52:17 -07:00

test_driver.dart

Don't try to stop the same app twice in flutter_attach test (#20905 )

2018-08-22 17:13:34 +01:00

test_utils.dart

Improve flutter tools integration tests (#18865 )

2018-07-10 06:51:12 +01:00

README.md

Integration tests

These tests are not hermetic, and use actual Flutter SDK. While they don't require actual devices, they run flutter_tester to test Dart VM and Flutter integration.

Some of these tests change the current directory for the process, so only one test can be run at a time. Use this command to run:

../../bin/cache/dart-sdk/bin/pub run test -j1