Skip to content

Filter the ADB logcat messages to the running application/test suite #143458

@matanlurey

Description

@matanlurey

Currently the (Android) scenario_app has very rudimentary logging, including dumping the full adb logcat to stdout:

  1. Starting adb logcat in the Dart process.
  2. On trap ... EXIT, dumps the logs to stdout.

Ideally, we'd filter and only show messages relevant to the running app (or test suite). Must haves:

This work is somewhat important, because debugging these tests on CI (and even locally) is non-trivial, and we suspect cases where certain tests are not running, or not taking screenshots consistently (at least on CI). Logging would be one part of feeling more certain that the tests are running as expected.

Log filtering historically has been brittle, so it might be good to have some small tests that verify this keeps working.

Tip

The Flutter tool does something like this, so maybe pick @christopherfujino or @jonahwilliams 🧠 .

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work liste: scenario-appThe `testing/scenario_app` fixture in the engineplatform-androidAndroid applications specificallyteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions