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

Offen
#331 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
32/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Ruhig
Tech-Stack
dart, go, playwright
Bereich
devtools, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Go
Sterne
6
Forks
3
Ø Merge
6 Std. 28 Min.
Gemergte PRs (30 T.)
362

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AlphaWaveSystems/flutter-probe

Alle Issues in AlphaWaveSystems/flutter-probe

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.