3a17b67353
Towards https://github.com/flutter/flutter/issues/51421. Asserts some state we would not like to be hit by in integration tests using `Flutter*TestDriver`. In addition, adds a tag that can be used to run all tests that currently use this pattern: ```sh flutter test --tags flutter-test-driver ``` This showcases processes leaking quite a bit: <https://gist.github.com/matanlurey/190d9084d3a45bc5737b8406bc05b4cd>.
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.