[tests] moving testing helpers under flutter/test to separate _flutter_test_helpers package #55515
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We'd like to support
flutter run -d chrome testfilein the flutter framework (#55512), since this supports a significantly better debugging experience than flutter test --platform chrome. A blocker to adopting that is compilation errors caused by the usage of test helpers imported via relative paths.Due to the generated entry point required in web builds (to bootstrap the rendering, much like the android/iOS hosts do on mobile), the compiler has difficulty resolving these paths.
For regular apps this isn't an issue since the compiler can convert the imports using the package scheme information. Since test files don't actually live in a package, this doesn't work for them.
To fix this, we can hoist these test helpers into their own package and make them a dev_dependency of the framework.