27c6cdb416
Roll dependendencies This rolls depdendencies to latest using flutter update-packages --force-upgrade This change includes three code changes: * Removes charcode from the dependencies allowlist since it no longer appears in the transitive closure of dependencies of the flutter, flutter_test, flutter_driver, flutter_localizations, and integration_test packages. * Uses Resolver.create instead of the deprecated Resolver constructor. The default Resolver constructor has been deprecated in favour of the static Resolver.create() factory function, which unfortunately happens to be async. Propagated the async-ness up the chain. This change was partially reverted and the deprecation ignored in this patch until package:coverage can be rolled internally at Google. * Eliminates the use of the deprecated packagesPath parameter to HitMap.parseJson. This parameter was deprecated and replaced with packagePath in https://github.com/dart-lang/coverage/pull/370 which was part of the overall deprecation of the .packages file in Dart itself https://github.com/dart-lang/sdk/issues/48272. The overall goal being that end-user code shouldn't need to know about implementation details such as whether dependency information is stored in a .packages file or a package_info.json file, but rather use the package_config package to obtain the package metadata and perform other functions such as resolving its dependencies to filesystem paths. packagesPath was replaced by packagePath, which takes the path to the package directory itself. Internally, package:coverage then uses package_config to do the rest of the package/script URI resolution to filesystem paths. This change was partially reverted and the deprecation ignored in this patch until package:coverage can be rolled internally at Google. This is a pre-update prior to updating flutter_template_images in https://github.com/flutter/flutter/pull/103739 Issue: https://github.com/flutter/flutter/issues/103371 Issue: https://github.com/flutter/flutter/issues/103775 Issue: https://github.com/flutter/flutter/issues/103830 When re-applying the partially-reverted changes to code coverage, we'll need to patch host_entrypoint.dart internally to await the Future that we'll be returning rather than a non-async value.
Private Test Runner
These are tests of private interfaces that can't easily happen in the regular flutter tests due to problems with test and implementation interdependence.
This gets around the problem of parts existing in more than one library by making a copy of the code under test.
The test script bin/test_private.dart tests private interfaces by copying the
code under test into a temporary workspace. The test is then free to make the
copied flutter source into a "part" of its own library by declaring a library
and using the part directive with a relative path to include the parts. This
way the test and the private interface are part of the same library, and the
private interface can be accessed by the test.
The tests are run like so:
dart run bin/test_private.dart
One limitation is that the copied private API needs to be separable enough to be copied, so it needs to be in its own separate files.
To add a private test, add a manifest file of the form (assuming "my_private_test" is the name of the test) to the test subdir:
{
"tests": [
"my_private_test.dart"
],
"pubspec": "my_private_test.pubspec.yaml",
"deps": [
"lib/src/subpackage/my_private_implementation.dart",
]
}
It will copy the files in deps relative to the packages/flutter directory
into a similar relative path structure in the test temporary directory tree. It
will copy the pubspec file into pubspec.yaml in the test temporary
directory, and copy all of the tests into the top of the test temporary
directory tree.
Each test gets its own temporary directory tree under a generated temporary
directory in the system temp dir that is removed at the end of the run, or under
the path given to --temp-dir on the command line. If a temporary directory is
given explicitly, it will not be deleted at the end of the run.