-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
flutter/packages
#4494Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work lista: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem teamTriaged by Ecosystem team
Description
Currently the way integration tests and native Android UI tests are run in flutter/plugins is via Firebase Test Lab, but we can only run those jobs for PRs from contributors. That means we're missing our most critical Android test coverage in presubmit for non-contributor PRs.
We should add a set of shards that run integration tests via Android emulators on Cirrus (example) to close that coverage gap.
We will likely need to rethink the existing coverage so that we're not just adding to our already-significant time+resource usage for Android tests. Things we could consider:
- Making the FTL tests post-submit only
- Removing one of the two FTL device configurations
/cc @blasten
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work lista: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem teamTriaged by Ecosystem team