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 摘要。