Offline brainstorming with @collinjackson :

One option would be to rely on pub dependency_overrides: when running the test. I'm imagining something like:

cd url_launcher_web

# Runs the url_launcher unit tests:
flutter test --with_package=/path/to/url_launcher

# Runs the url_launcher e2e tests:
flutter test -d chrome --with_package=/path/to/url_launcher/example

The --with_package argument means we're running tests from another package (url_launcher), while including the current directory as a path dependency (either as a new dependency or as a dependency override if it is already a dependency). The mechanism of adding that dependency is to be discussed, could potentially be modifying pubspec.yaml or pub tool command line argument.

The same concept should apply to running the example app:

cd url_launcher_web

# Runs the url_launcher example app:
flutter run -d chrome --with_package=/path/to/url_launcher/example

We still need a way to add some platform-specific examples/tests, if the example app isn't modular this might mean we have a separate example app in url_launcher_web that exercises only the platform-specific features (and same for e2e tests).

Edit: renamed --app-facing--plugin to --with-package, and added a section for flutter run

Example app and test code sharing between endorsed implementations #46716

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions