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

Aberta
#331 3 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
32/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Pouca atividade
Stack de tecnologia
dart, go, playwright
Domínio
devtools, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Go
Estrelas
6
Forks
3
Merge médio
6h 28min
PRs com merge (30d)
362

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de AlphaWaveSystems/flutter-probe

Todas as issues de AlphaWaveSystems/flutter-probe

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.