integration-testing

Validates natural-language Ableton agent workflows against a runner-owned Live process with deterministic assertions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Testing an AI agent that controls Ableton Live is hard because natural-language prompts produce nondeterministic behavior and assistant prose cannot be trusted as proof of success. This Skill provides a deterministic harness that runs reviewed scenario manifests against a real, runner-owned Live process and verifies exact project mutations through bridge reads and postcondition assertions. ## Core Features & Use Cases - Deterministic scenario execution: Run pnpm live:agent-smoke to execute reviewed scenario manifests with explicit tool allowlists, budgets, and cleanup assertions against a fresh Live Set. - Failure triage and layered reproduction: Classify failures across agent planning, approval policy, tool, bridge/protocol, Remote Script/LOM, assertion, timeout, and cleanup layers, then reproduce at the narrowest deterministic layer. - Coverage expansion guidance: Add new real-Live scenarios only after unit, protocol, bridge, tool, and workflow regression tests exist, with strict safety rules such as never using --approve-all or broadening allowlists to force a pass. - Use Case: After modifying the Python Remote Script, run the smoke suite so the harness reinstalls the script, launches a fresh Live process, and verifies scenarios like creating an 808 track or writing four-on-the-floor MIDI notes with exact note-content assertions. ## Quick Start Ask the agent to run the Ableton integration smoke suite with pnpm live:agent-smoke and triage the first failing scenario using the failure-triage reference.

Frequently Asked Questions about integration-testing

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

FAQPage Schema
How do I run Ableton agent integration tests?

Run pnpm live:agent-smoke after confirming your normal Ableton Live process is closed. The harness launches its own runner-owned Live process, executes scenario manifests, and prints a machine-readable evidence path plus traces for any failed scenario.

How do I debug a failing Ableton agent scenario?

Stop at the first failure and classify it using the failure-triage reference, which maps evidence to layers like agent planning, approval policy, bridge/protocol, and Remote Script/LOM. Reproduce the issue at the narrowest deterministic layer, such as a direct bridge command, before rerunning the agent prompt.

When should I add a new real-Live test scenario?

Add a scenario when a change introduces a user-facing natural-language workflow whose success depends on real Live behavior, and only after unit, protocol, bridge, tool, and workflow regression tests exist. Never add real-Live scenarios for renderer-only layout or styling changes.

Can I use this for Electron desktop UI or visual testing?

No. This Skill explicitly excludes visual Electron UX, layout, progress, approval, and cross-app computer-use testing. Those changes require component tests, Electron Playwright tests, and visual desktop UX testing instead.

Why does the harness forbid approving all tool calls?

The --approve-all flag is banned because scenarios must enforce reviewed tool allowlists, risk classes, budgets, and argument guards. Broadening approvals to make a failure pass defeats the purpose of deterministic verification and can mask real defects.