mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
edf26e756d
* Move web integration tool tests to web.shard Web integration tool tests depend on DDC changes in SDK. This change moves them to a separate shard and subshard so CI bot configurations can run them separately. In particular, with will allow running those tests on dart CI flutter HHH web bot instead of a non-web one, allowing early detection and easy classification of issues caused by SDK changes as VM- or Web related. * Enabled verbose mode for flaky web_tool_tests * Split out the test changes to be commited first
18 lines
682 B
Markdown
18 lines
682 B
Markdown
# 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):
|
|
|
|
```shell
|
|
../../bin/cache/dart-sdk/bin/pub 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.
|