History

[O] Removing all timeouts (mark II) (#26736 )

These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time.

2019-01-19 00:31:05 -08:00

test_data

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

daemon_mode_test.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

debugger_stepping_test.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

expression_evaluation_test.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

flutter_attach_test.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

flutter_run_test.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

hot_reload_test.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

lifetime_test.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

README.md

Remove -j1 to run tools tests concurrently (#22038 )

2018-09-19 17:47:06 +01:00

test_driver.dart

[O] Removing all timeouts (mark II) (#26736 )

2019-01-19 00:31:05 -08:00

test_utils.dart

Give integration tests unique temp folder names (#26227 )

2019-01-17 11:29:18 +00: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.

Use this command to run:

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