flutter/packages/flutter_tools/test/integration.shard
2019-12-10 10:26:14 -08:00
..
test_data License update (#45373) 2019-11-27 15:04:02 -08:00
daemon_mode_test.dart Revert "[flutter_tool] Prevent accidental calls to io.exit when asserts are active in unit tests (#46210)" (#46630) 2019-12-09 13:13:59 -08:00
debugger_stepping_test.dart License update (#45373) 2019-11-27 15:04:02 -08:00
expression_evaluation_test.dart License update (#45373) 2019-11-27 15:04:02 -08:00
flutter_attach_test.dart License update (#45373) 2019-11-27 15:04:02 -08:00
flutter_run_test.dart License update (#45373) 2019-11-27 15:04:02 -08:00
hot_reload_test.dart [flutter_tool] add a vmservice API for hot ui requests (#45649) 2019-12-09 21:31:34 -08:00
lifetime_test.dart License update (#45373) 2019-11-27 15:04:02 -08:00
README.md Some minor cleanup for flutter_tools (#36569) 2019-07-24 10:58:09 -07:00
test_driver.dart [flutter_tool] Reland: support --fast-start for Android applications (as an opt-in) (#46140) 2019-12-10 10:26:14 -08:00
test_utils.dart Revert "[flutter_tool] Prevent accidental calls to io.exit when asserts are active in unit tests (#46210)" (#46630) 2019-12-09 13:13:59 -08:00

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.