acceptance-tests
Read this before writing or running the graphical acceptance suite under `test/acceptance.d/`.
Claude Code
$ npx -y skills add omacom/omarchy --agent claude-code
Cursor
Cursor also loads subagents from .claude/agents, so copy this file there to use it in Cursor.
Agent definition
acceptance-tests.mdAcceptance Tests
Read this before writing or running the graphical acceptance suite under `test/acceptance.d/`.
The graphical acceptance suite lives in `test/acceptance` with test files under `test/acceptance.d/*-test.sh`. It exercises a real installed Omarchy desktop, including session health, shell surfaces, panels, keyboard navigation, representative applications, and system setup. Source `test/acceptance.d/base-test.sh` for the shared helpers.
Run acceptance tests in a disposable VM through the sibling `omarchy-iso` repository, not in the active development session. The suite opens and closes applications and temporarily changes desktop configuration.
For acceptance-test-only changes, reuse an installed base and sync the suite:
cd ../omarchy-iso
./bin/omarchy-iso-test release/<iso>.iso --reuse-base --sync-omarchy ../omarchy --no-preview
Use `--sync-all ../omarchy` instead of `--sync-omarchy ../omarchy` when the acceptance run must exercise local `bin/`, `config/`, or `shell/` source too. Changes to package manifests, installation, finalization, or shipped defaults require a fresh ISO built from the local checkouts and a run without `--reuse-base`:
cd ../omarchy-iso
./bin/omarchy-iso-make --no-boot-offer --local-source ../omarchy ../omarchy-pkgs
./bin/omarchy-iso-test release/<generated-iso>.iso --no-preview
Keep unrelated acceptance workflows in separate test files. The runner records a failed file and continues with the remaining files, which preserves as much diagnostic coverage as possible. Restore modified user state with traps, close anything the test opens, and capture every visually distinct state (including entered input where relevant) as `success-<step>.png`; failure helpers capture `failure-<step>.png`. The ISO harness collects the screenshots and logs under its timestamped `test-runs/` directory and opens the screenshots after the run unless `--no-preview` is passed.
The ISO harness exercises compositor-level shortcuts with QMP virtual keyboard input. In-guest `wtype` is suitable for typing into focused controls, but it does not reliably prove that a global Hyprland keybinding works.
Read more
Acceptance Tests
Read this before writing or running the graphical acceptance suite under `test/acceptance.d/`.
The graphical acceptance suite lives in `test/acceptance` with test files under `test/acceptance.d/*-test.sh`. It exercises a real installed Omarchy desktop, including session health, shell surfaces, panels, keyboard navigation, representative applications, and system setup. Source `test/acceptance.d/base-test.sh` for the shared helpers.
Run acceptance tests in a disposable VM through the sibling `omarchy-iso` repository, not in the active development session. The suite opens and closes applications and temporarily changes desktop configuration.
For acceptance-test-only changes, reuse an installed base and sync the suite:
cd ../omarchy-iso ./bin/omarchy-iso-test release/<iso>.iso --reuse-base --sync-omarchy ../omarchy --no-preview
Use `--sync-all ../omarchy` instead of `--sync-omarchy ../omarchy` when the acceptance run must exercise local `bin/`, `config/`, or `shell/` source too. Changes to package manifests, installation, finalization, or shipped defaults require a fresh ISO built from the local checkouts and a run without `--reuse-base`:
cd ../omarchy-iso ./bin/omarchy-iso-make --no-boot-offer --local-source ../omarchy ../omarchy-pkgs ./bin/omarchy-iso-test release/<generated-iso>.iso --no-preview
Keep unrelated acceptance workflows in separate test files. The runner records a failed file and continues with the remaining files, which preserves as much diagnostic coverage as possible. Restore modified user state with traps, close anything the test opens, and capture every visually distinct state (including entered input where relevant) as `success-<step>.png`; failure helpers capture `failure-<step>.png`. The ISO harness collects the screenshots and logs under its timestamped `test-runs/` directory and opens the screenshots after the run unless `--no-preview` is passed.
The ISO harness exercises compositor-level shortcuts with QMP virtual keyboard input. In-guest `wtype` is suitable for typing into focused controls, but it does not reliably prove that a global Hyprland keybinding works.
Omarchy is a beautiful, fun & agentic Linux distribution by DHH. Read more at omarchy.org.
Other agents on omarchy.
More agents from other plugins.
architect
AgentMUST BE USED when starting new projects or planning major changes. This agent specializes exclusively in system architecture…
api-reference
Agent**⚠️ DEVELOPER REFERENCE ONLY** — This file documents the raw GraphQL API schema for development and maintenance purposes (adding…
architect
AgentProduce design + contracts (OpenAPI/AsyncAPI/JSON Schema) + ADRs for a greenfield feature. Wraps /plan. Use when the spec exists…
Questions about acceptance-tests.
- Which coding agents can use acceptance-tests?
- acceptance-tests installs in Claude Code and Cursor: each loads subagents from .claude/agents, so copy the file there. Flowy's auto-invocation runs in Claude Code only.

