Cloud: provider for the Google Developer Device Platform (replaces Firebase Test Lab)

Open
#434 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
flutter, go

Research direction

Start by verifying the Google Developer Device Platform details listed in the acceptance criteria against the linked migration guide and the official API documentation. Write a short design note in the PR with verified facts and URLs before proposing a provider. The issue names no repository files or tests; done means the design note establishes whether a provider is viable, with implementation conditional on those findings.

Written by the indexing model from the issue text.

Description

area/cloud enhancement

Why

Firebase Test Lab "is deprecated and will be fully shut down on September 30, 2027" (https://firebase.google.com/docs/test-lab, read 2026-10-14). Google points to the Developer Device Platform on Google Cloud.

What the migration guide says (read 2026-10-14, https://docs.cloud.google.com/developer-device-platform/device-run/migrate)

  • It is driven by gcloud beta device-run (sessions submit instrumentation for Android, gcloud alpha device-run sessions submit xctest for iOS, plus devices and software-versions).
  • The guide lists Android instrumentation and iOS XCTest. It does not mention Robo tests, Appium, real iOS devices or a REST API (only the CLI and a Device Catalog API).

Why this is not a drop-in

The current firebase provider starts a Robo test and keeps the app alive while the agent talks to a relay. Robo is not listed for the new platform, so a replacement needs its own design (an instrumentation test that keeps the app alive, or the platform's session model).

Acceptance criteria

  • Verify online, before any code: the platform's API surface (REST or only the CLI), authentication, how to upload an app, how a long-lived session can keep the app running, and whether iOS devices are real or simulated.
  • A short design note in the PR (no code) with the verified facts and URLs, then a provider only if the design holds.
  • Keep the firebase provider until the shutdown date; remove it deliberately afterwards.

Not started on purpose.

Dominant language
Go
Stars
6
Forks
3
Avg merge
6h 28m
Merged PRs (30d)
362

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AlphaWaveSystems/flutter-probe

All issues in AlphaWaveSystems/flutter-probe

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.