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

Aperta
#434 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Tranquilla
Stack tecnologico
flutter, go

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
6
Fork
3
Merge medio
6h 28m
PR unite (30g)
362

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AlphaWaveSystems/flutter-probe

Tutte le issue di AlphaWaveSystems/flutter-probe

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.