development/flutter
development/flutter
1
0
Fork 0
mirror of https://github.com/flutter/flutter synced 2024-10-13 11:42:54 +00:00
Code Issues Packages Projects Releases Wiki Activity
flutter/packages/flutter_tools/test/integration.shard
History
Danny Tuppeny e8c5d66b5a
Use processManager.run() instead of manually capturing streams in test_utils getPackages() (#41687) 
* Capture stdout in test helper

* Simplify running getPackages() in test utils

* Remove unused import
2019-10-10 07:47:26 +01: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 Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108) 2019-07-13 11:51:44 -07:00
debugger_stepping_test.dart Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108) 2019-07-13 11:51:44 -07:00
expression_evaluation_test.dart update dependencies; add a Web smoke test (#37816) 2019-08-09 09:58:49 -07:00
flutter_attach_test.dart Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108) 2019-07-13 11:51:44 -07:00
flutter_run_test.dart Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108) 2019-07-13 11:51:44 -07:00
hot_reload_test.dart update dependencies; add a Web smoke test (#37816) 2019-08-09 09:58:49 -07:00
lifetime_test.dart Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108) 2019-07-13 11:51:44 -07:00
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 Use processManager.run() instead of manually capturing streams in test_utils getPackages() (#41687) 2019-10-10 07:47:26 +01: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.