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

未关闭
#434 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
flutter, go

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Go
星标
6
派生
3
平均合并
6 小时 28 分钟
30 天内合并 PR
362

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AlphaWaveSystems/flutter-probe 的其他 Issue

查看 AlphaWaveSystems/flutter-probe 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。