Studio: drive and test without computer-use (browser-mode E2E + Studio MCP tools)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
32/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
dart, go, playwright
领域
devtools, testing

调研方向

Start by reading the Studio E2E suite, the Wails app bindings, and the existing probe-mcp tools; the issue does not name their file paths. Check how wails dev exposes Go bindings and how the current tests drive the UI. Done means the UI suite runs headless, the opt-in native smoke suite remains available, and MCP clients can control a Studio run and read progress with the automation endpoint protected as specified.

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

描述

area/studio

The Studio E2E suite drives the real window with accessibility + cliclick, which takes over the cursor and focus of the machine it runs on. Most of Studio's behaviour is Go methods behind a web frontend and can be exercised without a visible window.

Proposal

  1. Browser-mode E2E. Run wails dev (frontend at localhost:34115 with live Go bindings) and drive it with headless Playwright. Port the UI tests (workspace, device picker, connect, run pass/fail, perf lines, recorder, settings, AI overlay, error paths, live step highlight) to it. No window, cursor or focus involvement; runs on any CI runner with a simulator.
  2. Native smoke set. Keep a small real-window suite (launch, window appears, WebKit-only controls) on the existing accessibility driver, opt-in (make studio-e2e-native), placed on the secondary display.
  3. Studio automation endpoint. Opt-in PROBE_STUDIO_AUTOMATION=1: localhost-only control socket with a per-launch token exposing the bound App methods plus a UI-state query (current file, device, run/step state, results) and a view screenshot.
  4. MCP tools in probe-mcp: studio_open_workspace, studio_list_devices, studio_connect, studio_run_file, studio_cancel, studio_run_state (current step), studio_results, studio_screenshot. Update MCP tool descriptions and docs/mcp.md.

Acceptance

  • Full UI suite runs headless with no visible window and no effect on mouse or focus.
  • An MCP client can open a workspace, connect, run a .probe file and read step-by-step progress.
  • Automation endpoint is off by default and refuses non-localhost and missing/incorrect token.
主要语言
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 摘要。