History

Handle a SocketException thrown when sending the browser close command to Chrome (#151197 )

https://github.com/flutter/flutter/pull/150645 tries to shut down Chrome by sending a browser close command through a debug protocol.  The webkit_inspection_protocol library used to send the command may throw a SocketException if Chrome has already been shut down.

2024-07-03 13:23:20 +00:00

test_data

Reland: Update link branches to main (#146882 )

2024-04-17 13:16:33 +00:00

chrome_test.dart

Handle a SocketException thrown when sending the browser close command to Chrome (#151197 )

2024-07-03 13:23:20 +00:00

debugger_stepping_web_test.dart

…

expression_evaluation_web_test.dart

…

hot_reload_web_test.dart

Flutter Web Bootstrapping Improvements (#144434 )

2024-03-12 22:41:26 +00:00

output_web_test.dart

[flutter_tool] Delete skipped tests (#136364 )

2023-10-11 10:24:14 -07:00

README.md

Added missing code block language in docs (#147481 )

2024-05-01 14:44:27 +00:00

vm_service_web_test.dart

…

web_driver_service_test.dart

Switch to more reliable flutter.dev link destinations in the tool (#150587 )

2024-06-26 23:30:39 +00:00

web_run_test.dart

…

README.md

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.