desktop-ux-testing

Validates Electron desktop UI changes through automated end-to-end testing with Ableton Live.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/CooperNederhood/Ableton-Agent-App --skill desktop-ux-testing-coopernederhood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-ux-testing
Source: https://github.com/CooperNederhood/Ableton-Agent-App/tree/main/.github/skills/desktop-ux-testing
Command: npx skills add https://github.com/CooperNederhood/Ableton-Agent-App --skill desktop-ux-testing-coopernederhood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that Electron UI changes actually work in the real desktop app requires manual clicking through both the app and Ableton Live, which is slow, error-prone, and easy to skip. This Skill provides a repeatable loop for visually validating desktop behavior end to end. ## Core Features & Use Cases - Automated UX validation loop: Build, launch a dedicated Ableton instance and the app in automation mode, send a message via the debug MCP tool, and inspect both apps with computer-use. - Isolated test environments: Uses fresh automation profiles and a runner-owned Live process so user data and existing Live Sets are never touched. - Result classification: Explicitly classifies outcomes as Completed, Failed, Blocked, or Inconclusive based on visible evidence in both applications. - Use Case: After changing how approval prompts render in the Electron app, use this Skill to launch the app, send a request that triggers an approval, and confirm the prompt displays correctly while Ableton Live reflects the expected change. ## Quick Start Use the desktop-ux-testing skill to validate my recent changes to the approval dialog by launching the app and Ableton, sending a test message, and inspecting the result.

Frequently Asked Questions about desktop-ux-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test Electron app UI changes end to end?

Build the workspace, launch a dedicated Ableton instance with pnpm live:ux-host, start the app in automation mode with an isolated profile, send a message through the debug MCP tool, and inspect both apps with computer-use. Repeat the loop until observed behavior matches expectations.

How do I send messages to the desktop app during automated testing?

Use the send_user_message tool from the registered local stdio MCP server, which reads a stable automation descriptor file. Verify the descriptor's processId matches the exact Desktop process started for the run before sending.

Can I test against an already running Ableton Live instance?

No. The skill requires launching a dedicated runner-owned Live process via pnpm live:ux-host and never reusing or taking control of a user's pre-existing Live process. This ensures known startup-dialog handling and exact process ownership.

When should I use deterministic integration tests instead of visual UX testing?

Use the deterministic pnpm live:agent-smoke workflow when requirements depend on exact MIDI notes, clip or track counts, ordering, rollback, mutation budgets, or protocol behavior. Visual inspection cannot verify these precise postconditions.

Why does MCP tool success not mean my message was processed?

MCP success only confirms the Desktop app accepted the message. You must still verify the turn visibly completed in the renderer and that Ableton Live shows the expected result before classifying the test as passed.