-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable more tests in flutter/packages #102851
Comments
It turns out |
For |
This brings the Cirrus configuration more in line with flutter/plugins, to reduce testing diffs between the two repositories: - Updates naming and grouping comments to match flutter/plugins to make them easier to compare. - Enables building examples on all platforms. This was being done for Android, and iOS, and Windows, but not Linux, macOS, or web, which wasn't an intentional mismatch. - Enables 'flutter drive' tests for web. - Does not enable them for other platforms as currently there is no need for them, and setup is non-trivial on some platforms (FTL secrets for Android, new Dockerfile dependencies for Linux). - Enables native unit tests for all platforms. (In practice this is a no-op at the momement, but it's a very fast no-op that doesn't require extra setup.) Rolls repo tooling forward to pick up support for `drive-examples` in non-plugin packages, and for running Dart unit tests in examples. Fixes flutter/flutter#102851
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Apparently we have some flutter driver tests in the repo; we don't currently run
drive-examples
on any platform. We also don't build examples on web or any of the desktop platforms.We should add all of that to the CI so that anything that's added to the repo actually runs.
(I'll also audit for other differences; I happened to find today that
readme-check
was never turned on, and there may be other new checks that haven't been enabled for the packages repo.)The text was updated successfully, but these errors were encountered: