History

Reland: don't update last compile time when compilation is rejected. (#41580 )

* dont update last compiled time when compilation is rejected

* lets try flushing, thats a neat trick

* windows man

* Update hot_reload_test.dart

* Update hot_reload_test.dart

* Update devfs.dart

* Update hot_reload_test.dart

* Update hot_reload_test.dart

* add test that verifies when compile is good that time is updated

* Update devfs_test.dart

2019-10-02 12:46:33 -07:00

test_data

Reland: don't update last compile time when compilation is rejected. (#41580 )

2019-10-02 12:46:33 -07:00

daemon_mode_test.dart

…

debugger_stepping_test.dart

…

expression_evaluation_test.dart

update dependencies; add a Web smoke test (#37816 )

2019-08-09 09:58:49 -07:00

flutter_attach_test.dart

…

flutter_run_test.dart

…

hot_reload_test.dart

update dependencies; add a Web smoke test (#37816 )

2019-08-09 09:58:49 -07:00

lifetime_test.dart

…

README.md

Some minor cleanup for flutter_tools (#36569 )

2019-07-24 10:58:09 -07:00

test_driver.dart

fix bad indentations(mainly around collection literals) (#41355 )

2019-09-27 10:46:45 +02:00

test_utils.dart

[flutter_tool] Use curly braces around single statment control structures (#40446 )

2019-09-13 14:51:35 -07:00

README.md

Integration tests

These tests are not hermetic, and use the 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 (from the flutter_tools directory):

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

These tests are expensive to run and do not give meaningful coverage information for the flutter tool (since they are black-box tests that run the tool as a subprocess, rather than being unit tests). For this reason, they are in a separate shard when running on continuous integration and are not run when calculating coverage.