History

Skip tests that are expected to fail with timeouts (#20074 )

* Skip tests instead of expecting failure, because expected failure = timeout which is slow

Some of these tests are known to fail and were coded to expect it; however because the failure is a timeout it's just dragging out test runs (shortening timeouts will make the tests flakier).

* Make it easier to find skipped tests

* Change SKIP to TODO

2018-08-01 17:50:38 +01:00

test_data

Look up breakpoints rather than relying on magic numbers (#19708 )

2018-07-25 15:31:57 +01:00

expression_evaluation_test.dart

Fix copy/paste error in test (#19564 )

2018-07-19 19:52:15 +01:00

flutter_attach_test.dart

Skip tests that are expected to fail with timeouts (#20074 )

2018-08-01 17:50:38 +01:00

flutter_tester_test.dart

Improve flutter tools integration tests (#18865 )

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

hot_reload_test.dart

Skip tests that are expected to fail with timeouts (#20074 )

2018-08-01 17:50:38 +01:00

lifetime_test.dart

Skip tests that are expected to fail with timeouts (#20074 )

2018-08-01 17:50:38 +01:00

README.md

Integration test for FlutterTesterDevice. (#16424 )

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

test_driver.dart

Change from .first to .single to ensure this (#19981 )

2018-07-31 08:05:24 +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