mirror of
https://github.com/flutter/flutter
synced 2024-10-13 11:42:54 +00:00
56a7dacd46
After Dart VM change we are now required to use loadLibrary on an import whenever it is imported as deferred. See: https://dart-review.googlesource.com/c/sdk/+/149613 |
||
|---|---|---|
| .. | ||
| test_data | ||
| background_isolate_test.dart | ||
| command_output_test.dart | ||
| coverage_collection_test.dart | ||
| daemon_mode_test.dart | ||
| debugger_stepping_test.dart | ||
| debugger_stepping_web_test.dart | ||
| downgrade_upgrade_integration_test.dart | ||
| expression_evaluation_test.dart | ||
| expression_evaluation_web_test.dart | ||
| flutter_attach_test.dart | ||
| flutter_run_test.dart | ||
| gen_l10n_test.dart | ||
| hot_reload_test.dart | ||
| lifetime_test.dart | ||
| README.md | ||
| stateless_stateful_hot_reload_test.dart | ||
| test_driver.dart | ||
| test_utils.dart | ||
| vmservice_integration_test.dart | ||
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.