Description
This will be a followup to:
After we have the Android build running in our own CI, we should register it in Flutter's "customer tests" (like we did with our flutter analyze
and flutter test
as #239) so that it runs as part of Flutter's CI too. In particular this would have caught #771 at an earlier stage — the PR that made that change in the Flutter repo would have already seen a test failure.
I think there aren't any existing tests of this kind in the flutter/tests registry, and it's possible it'll call for some augmenting of that system's API. In particular it runs each test suite for 10 iterations by default, to catch flakes; but an Android build is a lot slower than a flutter test
run on a comparable size of app, enough to make that expensive. Plus when it's purely a build, it's hard to imagine it flaking. So we may want to run that test for only 1 iteration, while still running our flutter test
for 10 iterations. Anyway, that'll be a subject to raise in #hackers-tests
in Discord if, when working on this issue, we decide something like that is indeed wanted.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
No status