flutter/packages/flutter_tools/test/web.shard
Matan Lurey 449079d4f1
Propagate environment variables when flutter drive is invoked. (#161452)
Closes https://github.com/flutter/flutter/issues/161449.

~3 LOC, with 203 lines of tests (including an e2e integration test that
it actually works).

Feedback welcome!

(The reason I'm working on this is the ability to pass environment
variables makes it much easier and less hacky to make
`android_engine_test` configurable, i.e. have different expected outputs
for OpenGLES/Vulkan, compare screenshots locally for deflaking, etc).
2025-01-13 18:48:58 +00:00
..
test_data Migrate apple-mobile-web-* to mobile-web-*. (#154964) 2024-09-11 00:39:51 +00:00
chrome_test.dart Auto-format Framework (#160545) 2024-12-19 20:06:21 +00:00
debugger_stepping_web_test.dart Auto-format Framework (#160545) 2024-12-19 20:06:21 +00:00
expression_evaluation_web_test.dart Auto-format Framework (#160545) 2024-12-19 20:06:21 +00:00
hot_reload_web_test.dart Auto-format Framework (#160545) 2024-12-19 20:06:21 +00:00
output_web_test.dart Auto-format Framework (#160545) 2024-12-19 20:06:21 +00:00
README.md Added missing code block language in docs (#147481) 2024-05-01 14:44:27 +00:00
vm_service_web_test.dart Auto-format Framework (#160545) 2024-12-19 20:06:21 +00:00
web_driver_service_test.dart Propagate environment variables when flutter drive is invoked. (#161452) 2025-01-13 18:48:58 +00:00
web_run_test.dart [tool] Removes deprecated --web-renderer parameter. (#159314) 2024-12-02 18:33:02 +00:00

Web 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 web debug services (dwds) and Flutter integration.

Use this command to run (from the flutter_tools directory):

../../bin/cache/dart-sdk/bin/dart run test test/web.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.