Skip to content

Difficult state of flutter_driver v integration_test #142021

@matanlurey

Description

@matanlurey

Context

I'm working on a critical Android platform feature, that, if not fixed (and kept fixed, i.e. by integration tests), blocks Impeller's launch on Android, and would create significant technical debt for the team (this part of the codebase is very fragile, and breakages have caused major internal and external escalations in the past1).

I found an existing integration test that is supposed to cover our use case, external_ui (I'm in the process of renaming it to android_surface_texture_integration_test to disambiguate, but currently it lives in dev/integration_tests/external_ui), which is written using flutter_driver.

Request

I can't find anywhere how to use this package (flutter_driver), only that I'm supposed to migrate to integration_test, but our own codebase hasn't done this migration (there are at least 63 occurrences in flutter/flutter) , and it appears that it's not feature complete or even actively maintained.

Here are some examples (very rough searching, there are likely more):

I am just not sure what I'm supposed to do :-/


/cc @Piinks given your issue #139249.

Footnotes

  1. Point of contact: @johnmccutchan or @reidbaker

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work lista: tests"flutter test", flutter_test, or one of our testsc: tech-debtTechnical debt, code quality, testing, etc.f: integration_testThe flutter/packages/integration_test pluginteam-frameworkOwned by Framework teamtriaged-frameworkTriaged by Framework team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions