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

Abierto
#434 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
flutter, go

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
6
Forks
3
Merge medio
6 h 28 min
PR fusionados (30 d)
362

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AlphaWaveSystems/flutter-probe

Todos los issues de AlphaWaveSystems/flutter-probe

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.